> For the complete documentation index, see [llms.txt](https://docs.complycube.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.complycube.com/documentation/api-reference/core-resources/documents.md). # Documents Documents can be linked to clients for additional verification checks and KYC record-keeping. **Documents** can be created for a given client for the following purposes: * Secure and centralised document storage. * Perform checks such as [**Document Checks**](https://docs.complycube.com/api-reference/check-types/document-check) and [**Identity Checks**](https://docs.complycube.com/api-reference/check-types/identity-check). The documents API allows you to create, update, retrieve, upload, and delete documents. You can fetch a specific document or retrieve a list of all your documents. {% hint style="info" %} To upload an image attachment, you first have to [**create a document**](/documentation/api-reference/core-resources/documents/create-a-document.md#create-a-document) object, then [**upload an image attachment**](/documentation/api-reference/core-resources/documents/upload-image-attachment.md). {% endhint %} ### The Document object

Attribute	Type	Description
`id`	string	The unique identifier for a document.
`clientId`	string	The ID of the client associated with this document.
`type`	string	The type of document. Valid values include: `passport` `driving_license` `national_insurance_number` `social_security_number` `utility_bill` `council_tax_bill` `tenancy_agreement` `insurance_document` `government_letter` `benefits_statement` `tax_identification_number` `national_identity_card` `visa` `polling_card` `residence_permit` `birth_certificate` `bank_statement` `financial_statement` `change_of_name` `tax_document` `signed_document` `company_confirmation_statement` `company_annual_accounts` `company_statement_of_capital` `company_change_of_address` `company_incorporation` `company_change_of_officers` `company_change_of_beneficial_owners` `vehicle_ownership_document` `property_ownership_document` `proof_of_ownership` `unknown` `other`
`classification`	string	The classification or purpose of this document. Valid values include: `proof_of_identity` `source_of_wealth` `source_of_funds` `proof_of_address` `company_filing` `other`
`documentNumber`	string	The document's number.
`issuingCountry`	string	The document's issuing country. This will be the two-letter country ISO code.
`issuingState`	string	The state that issued the document. This must be the state's USPS abbreviation (e.g. `NY`, `CA`, or `DE`).
`images`	array [object]	The images or attachments associated with the document. This will only appear once a document image is uploaded. Also, see the image object below.
`createdAt`	string	The date and time when the document was created.
`updatedAt`	string	The date and time when the document was updated.

#### The `image` object

Attribute	Type	Description
`id`	string	The unique identifier for a document image attachment.
`fileName`	string	The file name.
`documentSide`	string	The side of document: `front` or `back`.
`downloadLink`	string	The download link to the document image.
`contentType`	string	The content-type of the document image.
`size`	number	The size of the document image in bytes.
`createdAt`	string	The date and time when the image was created.
`updatedAt`	string	The date and time when the image was updated.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.complycube.com/documentation/api-reference/core-resources/documents.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.