List the documents | INFONITE

[
  {
    "sub_family": "attachment:es-tgss-life-report",
    "id": "6aa74d55cacbac2754cb62e4",
    "content_name": "work_life_report.pdf",
    "content_type": "application/pdf",
    "metadata": {
      "cea-id": "DEMO3E03CAB9",
      "csv-code": "DEMO0-3E03C-AB917-846EF-19093-A5A2A",
      "csv-url": "https://sandbox.infonite.tech/demo/verify",
      "document-date": "2026-09-12",
      "document-type": "attachment:es-tgss-life-report"
    },
    "product": "attachment",
    "content_hash": "d3df1044751484e3296222487667f33050fda5e1e5d80e159773bbcd2a9540212d5f64afa48e9318b2b93dca1077ad06fd79dfb64c2e58e56c6975528c024a47"
  },
  {
    "sub_family": "attachment:es-cirbe-report",
    "id": "6aa74daf9f005f6719cb62df",
    "content_name": "cirbe_report_es_cirbe_detailed.pdf",
    "content_type": "application/pdf",
    "metadata": {
      "document-date": "2026-09-12T03:28:15.068346+02:00",
      "document-type": "attachment:es-cirbe-report",
      "signature-verified": true
    },
    "product": "attachment",
    "content_hash": "80b3ad5dc1b5fec5eb7fb53ba9b9d6498ff4f2f13d82d50859445c22db0c1006c7fc66d817a17ba38523cd2b7f73a629281bb273b6081ae2c344a7c01ee195ec"
  }
]

Every original document the execution retrieved, described but not downloaded.

Engines do not only extract data: where the source issues a document — a Vida Laboral report, a tax declaration, a CIRBE report, a certificate — the original file is kept with the execution. This endpoint lists them all: what each one is (sub_family), its name, its content type, its size and the id you download it by. The catalogue of types is in Attachments.

The bytes are not here, on purpose. A response carrying half a dozen PDFs inline would be enormous and mostly unwanted. Read the list, decide what you need, and fetch each file with Download a document.

Results reference their own documents inline too — attachments inside a labor check, for instance — with the same identifiers. Both routes lead to the same files.

Status	Meaning
`200`	The documents. An empty list means the execution produced none.
`202`	`execution_still_processing` — this endpoint waits for the whole execution, unlike the per-family ones.
`404`	No execution with that id for your application, or it has been deleted.

Server to server only. This call is authorised with your application secret: it belongs in your backend, never in a browser, a mobile app or anything your customer can read.

Every original document the execution retrieved, described but not downloaded. Engines do not only extract data: where the source issues a document — a *Vida Laboral* report, a tax declaration, a CIRBE report, a certificate — the original file is kept with the execution. This endpoint lists them all: what each one is (`sub_family`), its name, its content type, its size and the `id` you download it by. The catalogue of types is in [Attachments](/guides/data-models/attachments). <Note> **The bytes are not here, on purpose.** A response carrying half a dozen PDFs inline would be enormous and mostly unwanted. Read the list, decide what you need, and fetch each file with [Download a document](api:GET/executions/results/{execution_id}/attachments/v1/{attachment_id}). </Note> Results reference their own documents inline too — `attachments` inside a labor check, for instance — with the same identifiers. Both routes lead to the same files. | Status | Meaning | | :--- | :--- | | `200` | The documents. An empty list means the execution produced none. | | `202` | `execution_still_processing` — this endpoint waits for the **whole** execution, unlike the per-family ones. | | `404` | No execution with that id for your application, or it has been deleted. | <Note> **Server to server only.** This call is authorised with your application secret: it belongs in your backend, never in a browser, a mobile app or anything your customer can read. </Note>

Authentication

X-APP-SECRETstring

Application Secret

Path parameters

execution_idstringRequiredformat: "object-id"

The execution, as the acceptance response returned it.

Response

200 OK
One entry per document the execution retrieved: what it is, its name, its content type, its size and the id you download it by. The bytes are not here, on purpose — a body carrying half a dozen PDFs would be enormous and mostly unwanted.

sub_familyenum

What kind of document this is (e.g. attachment:es-tgss-life-report).

idstringformat: "object-id"

Attachment identifier — use it to download the file through the execution’s attachments endpoint.

content_namestring

File name of the document.

content_typestringformat: "mime-type"

MIME type of the content.

metadatamap from strings to any

Extra facts about the document, as simple key-value pairs (e.g. its official verification code, its issue date).

product"attachment"OptionalDefaults to attachment

The product type identifier. Always attachment.

content_hashstringOptional

Fingerprint of the content, to verify its integrity.

Errors

404

Not Found Error

422

Unprocessable Entity Error

Every original document the execution retrieved, described but not downloaded.

Results reference their own documents inline too — attachments inside a labor check, for instance — with the same identifiers. Both routes lead to the same files.

Status	Meaning
`200`	The documents. An empty list means the execution produced none.
`202`	`execution_still_processing` — this endpoint waits for the whole execution, unlike the per-family ones.
`404`	No execution with that id for your application, or it has been deleted.

Server to server only. This call is authorised with your application secret: it belongs in your backend, never in a browser, a mobile app or anything your customer can read.