Attachments
Where it lives: on every result that carries documents — e.g.
data.employment.labor_check.attachments — and listed session-wide by the attachments
endpoint.
Many results carry the original documents they were extracted from — official PDF reports,
receipts — as attachments. The result itself only carries the attachment’s description; the
bytes are downloaded separately through the session’s attachments endpoint using the
attachment’s id, so payloads stay light and you fetch only the files you need.
Attachments follow the session’s lifetime: download what you want to keep while the session is available.
A document attached to a result — an official report, a receipt, an invoice... The entry
describes the file; its bytes are downloaded with id, through the attachments endpoint of the
API that returned the result.
What kind of document this is (e.g. attachment:es-tgss-life-report).
Attachment identifier — what the attachments endpoint of the API that returned the result takes to download the file.
Extra facts about the document, as simple key-value pairs (e.g. its official verification code, its issue date).
The product type identifier. Always attachment.
Document kinds
sub_family tells you what each document is:
Signed documents
Some documents carry their issuer’s digital signature. The Banco de España’s risk report (attachment:es-cirbe-report) is one of them, and its signature is checked against the Banco de España’s own certificates before the report reaches you. The verdict travels in the attachment’s metadata; a report whose check fails is still delivered, with the reason.