> ## Documentation Index > Fetch the complete documentation index at: https://docs.blockworksresearch.com/llms.txt > Use this file to discover all available pages before exploring further. # Get Filing Detail > Retrieve one published Token Transparency filing with its full content ## Overview This endpoint returns **one published Token Transparency filing** with its full content: the project, the filing metadata, the pinned schema (sections and question definitions), and the answers keyed by question id. Use the `filing_id` values from the [List Filings](/api-reference/token-transparency/list-filings) endpoint as the `id` path parameter. Unlike other Blockworks API endpoints, this endpoint is **public and does not require an API key**. ## Example Request ```bash cURL theme={null} curl "https://api.blockworks.com/v1/ttf/filings/35f94c78-ec1a-4061-8c74-6fd6a0b88a38" ``` ```typescript TypeScript theme={null} const response = await fetch( 'https://api.blockworks.com/v1/ttf/filings/35f94c78-ec1a-4061-8c74-6fd6a0b88a38' ) const data = await response.json() ``` ```python Python theme={null} import requests response = requests.get( 'https://api.blockworks.com/v1/ttf/filings/35f94c78-ec1a-4061-8c74-6fd6a0b88a38' ) data = response.json() ``` ### Example Response A successful response returns the project, the filing, the schema the filing was submitted against, and the answers. The example below is truncated to one section and two questions: one complete answer and one gap. ```json theme={null} { "project": { "project_slug": "mina-protocol", "protocol_name": "Mina Protocol", "protocol_ticker": "MINA" }, "filing": { "filing_id": "35f94c78-ec1a-4061-8c74-6fd6a0b88a38", "filing_type": "B1", "completion_label": "partial - 3 gaps", "filing_version": "1.3", "date_filed": "2026-08-17", "static_url": "https://blockworks.com/token-transparency/filing/mina-protocol", "filing_status": "current", "provenance": "issuer-filed" }, "schema": { "version_id": "1.3", "sections": [ { "name": "Project & Team", "questions": [ { "id": "q1", "label": "Description of Project", "config": { "mode": "fielded", "sub_fields": [ { "id": "q1a", "label": "Problem the project solves", "instructions": "The problem the project is solving." } ] }, "max_score": 5, "answer_type": "text", "instructions": "Provide a concise narrative that clearly states each of (a)-(e) below." } ] } ] }, "questions": { "q1": { "answer": { "sub_answers": [ { "sub_field_id": "q1a", "text": "Mina is presented as a public, decentralized layer-1 blockchain built to keep the chain extremely small while supporting zero-knowledge applications." } ] }, "gap": false, "label": "complete" }, "q8": { "answer": { "rows": [ { "market_maker_name": "N/A no current listings, historic listings unknown", "token_allocation": "N/A no current listings, historic listings unknown", "term_duration": "N/A no current listings, historic listings unknown", "structure_name": "N/A no current listings, historic listings unknown" } ] }, "gap": true, "label": "incomplete" } } } ``` ## Supported Options | Name | Type | Details | Available Options | | ---- | ---- | ------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------- | | `id` | path | Filing UUID from the List Filings endpoint. A malformed UUID returns a `400` error. An unknown or unpublished filing returns a `404` error. | e.g. `04c27d54-14c9-40a0-bd56-c9a9437c14df` | ## Response Fields | Field | Type | Description | | -------------------- | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `project` | object | The project the filing belongs to (`project_slug`, `protocol_name`, `protocol_ticker`) | | `filing` | object | Filing metadata, in the same shape as the List Filings endpoint | | `schema` | object | The schema version the filing was submitted against | | `schema.version_id` | string | Schema version identifier | | `schema.sections` | array | Ordered sections; each has a `name` and its question definitions. Each question has an `id`, a `label`, a `config` that describes the answer shape (`mode`: `fielded`, `open`, `sectioned`, or `grid`), a `max_score`, an `answer_type`, and its `instructions` | | `questions` | object | Answers keyed by question id (e.g. `q1`) | | `questions.*.answer` | object \| null | The published answer. Its shape follows the question's `config` in `schema.sections`: `sub_answers` for fielded text, `rows` for open and grid tables, `sections` for sectioned tables | | `questions.*.gap` | boolean | `true` when the reviewer marked the answer as a gap. A gap answer keeps its published content | | `questions.*.label` | string \| null | Completeness label: `incomplete`, `partially_complete`, or `complete`. `null` when no label is available | All answer text and table cell values are markdown strings. ## Notes * Responses are cached at the edge for up to 5 minutes (`Cache-Control: public, max-age=300`). * No API key or authentication header is needed for this endpoint. ## Related Endpoints * [List Filings](/api-reference/token-transparency/list-filings) ## OpenAPI ````yaml GET /v1/ttf/filings/{id} openapi: 3.0.0 info: title: Blockworks API description: '' version: 1.0.0 contact: {} servers: - url: https://api.blockworks.com security: - x-api-key: [] tags: [] paths: /v1/ttf/filings/{id}: get: tags: - ttf-public summary: Get Filing Detail description: >- Returns one published Token Transparency filing with its full content: the project, the filing metadata, the pinned schema (sections and question definitions), and the answers keyed by question id. This endpoint does not require an API key. operationId: PublicFilingsController_getDetail_v1 parameters: - name: id required: true in: path description: Filing UUID (`filing_id` from the List Filings endpoint) schema: type: string format: uuid responses: '200': description: '' content: application/json: schema: $ref: '#/components/schemas/PublicFilingDetailResponse' example: project: project_slug: mina-protocol protocol_name: Mina Protocol protocol_ticker: MINA filing: filing_id: 35f94c78-ec1a-4061-8c74-6fd6a0b88a38 filing_type: B1 completion_label: partial - 3 gaps filing_version: '1.3' date_filed: '2026-08-17' static_url: >- https://blockworks.com/token-transparency/filing/mina-protocol filing_status: current provenance: issuer-filed schema: version_id: '1.3' sections: - name: Project & Team questions: - id: q1 label: Description of Project config: mode: fielded sub_fields: - id: q1a label: Problem the project solves instructions: The problem the project is solving. max_score: 5 answer_type: text instructions: >- Provide a concise narrative that clearly states each of (a)-(e) below. questions: q1: answer: sub_answers: - sub_field_id: q1a text: >- Mina is presented as a public, decentralized layer-1 blockchain built to keep the chain extremely small while supporting zero-knowledge applications. gap: false label: complete q8: answer: rows: - market_maker_name: N/A no current listings, historic listings unknown token_allocation: N/A no current listings, historic listings unknown term_duration: N/A no current listings, historic listings unknown structure_name: N/A no current listings, historic listings unknown gap: true label: incomplete '400': description: Bad Request '404': description: Not Found security: [] components: schemas: PublicFilingDetailResponse: type: object properties: project: $ref: '#/components/schemas/PublicProjectResponse' filing: $ref: '#/components/schemas/PublicFilingResponse' schema: $ref: '#/components/schemas/PublicFilingDetailSchemaResponse' questions: type: object additionalProperties: $ref: '#/components/schemas/PublicQuestionResponse' required: - project - filing - schema - questions PublicProjectResponse: type: object properties: project_slug: type: string protocol_name: type: string protocol_ticker: type: string nullable: true required: - project_slug - protocol_name - protocol_ticker PublicFilingResponse: type: object properties: filing_id: type: string description: Unique filing identifier filing_type: type: string description: Filing type, e.g. B1 completion_label: type: string description: Completion summary, e.g. "complete" or "partial - 2 gaps" filing_version: type: string description: Version of the filing schema the filing was submitted against date_filed: type: string description: Publication date (UTC, YYYY-MM-DD) static_url: type: string description: Permalink to the filing on blockworks.com filing_status: type: string enum: - current - stale description: >- Whether the filing is current or stale (superseded or past its staleness deadline) provenance: type: string description: How the filing was produced, e.g. issuer-filed required: - filing_id - filing_type - completion_label - filing_version - date_filed - static_url - filing_status - provenance PublicFilingDetailSchemaResponse: type: object properties: version_id: type: string sections: type: array description: >- Ordered filing sections; each has a name and its question definitions items: type: object additionalProperties: true required: - version_id - sections PublicQuestionResponse: type: object properties: answer: type: object nullable: true additionalProperties: true description: >- The published answer; its shape follows the question's config in schema.sections gap: type: boolean description: True when the reviewer marked the answer as a gap label: type: string nullable: true description: >- Completeness label: incomplete, partially_complete, or complete; null when no label is available required: - answer - gap - label securitySchemes: x-api-key: type: apiKey in: header name: x-api-key ````