> ## Documentation Index > Fetch the complete documentation index at: https://entendre.ai/docs/llms.txt > Use this file to discover all available pages before exploring further. # Upload document > Uploads a base64-encoded file and returns its document ID and extracted summary. Requires `write:vault` and a user-associated API key. Entendre classifies the document. A bill can also post a journal entry, so upload only files that you intend to store and process. ## OpenAPI ````yaml openapi-public-preview.json POST /v1/vault/documents openapi: 3.1.0 info: title: Entendre API version: 1.0.0 description: Programmatic access to crypto-native accounting and treasury operations. servers: - url: https://api.entendre.finance description: Production API. security: - ApiKey: [] tags: - name: Organization description: Read your organization profile and find members for agent assignments. - name: Transactions description: Find transactions, inspect their details and create manual records. - name: Sources description: >- Manage wallets, exchange accounts, bank accounts and other transaction sources. - name: Assets description: Inspect asset acquisitions, remaining quantities and cost basis. - name: Journals description: >- Create and post journal entries, correct eligible entries and sync posted journals to a connected general ledger. - name: Documents description: >- Upload documents, check processing status and link supporting evidence to transactions. - name: Legal Entities description: Manage the legal entities used in your accounting records. - name: Ledger Accounts description: Manage your chart of accounts and find accounts for journal entries. - name: Tags description: Create and manage tags to classify your records. - name: Accruals description: >- Create and post accruals, inspect their status and reverse eligible entries. - name: Cash Application description: Match deposits to invoices and manage the resulting cash applications. - name: Classification description: >- Classify transactions in a batch, post eligible entries and inspect the results. - name: Revaluation description: Run asset revaluations for an accounting period and check their results. - name: Accounting Periods description: Check whether a period is ready to close, then close or reopen it. - name: Income Statement description: View revenue, expenses and net income for a reporting period. - name: Balance Sheet description: View assets, liabilities and equity as of a reporting date. - name: Trial Balance description: Review ledger account balances and debit and credit totals. - name: Closing Positions description: View asset positions at the end of a reporting period. - name: Treasury Balances description: Review treasury balances by asset and source. - name: Realized Gains & Losses description: Review realized gains and losses from asset dispositions. - name: Asset Tax Lots description: Inspect asset tax lots, remaining quantities and cost basis. - name: Schedule of Dispositions description: >- Review asset dispositions and their proceeds, cost basis and gains or losses. - name: Financial Insights description: Review financial insights for your selected reporting context. - name: Agents description: Create agents, schedule their work and inspect their runs. - name: Memory description: Read, search and maintain the memory files your agents use. - name: Connections description: Connect providers, manage authorization and disconnect. - name: GL Mapping description: >- Map ledger accounts and legal entities to your ERP. Import legal entities, tags and chart of accounts. - name: Request description: Request information, documents or connections from a client. - name: Client description: Manage your firm’s client relationships. - name: Team description: Invite team members and manage their access to your firm. - name: Settings description: Read and update your firm settings. paths: /v1/vault/documents: post: tags: - Documents summary: Upload document description: >- Uploads a base64-encoded file. Requires write:vault and a user-associated API key. Returns the document ID and extracted summary. Creating a bill can also post a journal entry. operationId: upload_document parameters: - name: Idempotency-Key in: header required: false description: >- Optional retry key. Check X-Idempotency-Applied before relying on replay protection. schema: type: string minLength: 1 maxLength: 255 example: example-operation-2026-08-31-001 requestBody: required: true content: application/json: schema: type: object required: - filename - base64 properties: filename: type: string minLength: 1 maxLength: 255 description: File name, including the extension. base64: type: string minLength: 1 description: >- Base64-encoded file contents. The base64 string is capped at 14 MB (~10.5 MB decoded). maxLength: 14680064 additionalProperties: false example: filename: note.txt base64: SGVsbG8= responses: '201': description: Uploaded document. content: application/json: schema: type: object required: - data properties: data: type: object required: - document_id - filename - document_type - summary - message properties: document_id: type: - string - 'null' description: Document ID (`doc_…`). filename: type: - string - 'null' description: File name. document_type: type: - string - 'null' description: Document type. summary: type: - string - 'null' description: Summary of the document. message: type: string description: Summary message. document: type: object additionalProperties: true description: The document. description: The uploaded document. example: data: document_id: doc_6f31e8c4-41ce-47af-9db7-3ad295a0a601 filename: invoice.pdf document_type: bill summary: Vendor invoice. message: File uploaded headers: Location: description: URL to retrieve the created document. schema: type: string example: /v1/vault/documents/doc_6f31e8c4-41ce-47af-9db7-3ad295a0a601 '400': description: >- The request is invalid. `error.fields` lists the fields to correct. Nothing was changed. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: code: VALIDATION_ERROR message: Invalid path, query or request body. request_id: req_example '401': description: The API key is missing, invalid or expired. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: code: UNAUTHORIZED message: Authentication is required. request_id: req_example '403': description: >- The API key does not have the required scope or is not associated with a user, or the action needs a review in the dashboard. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: code: FORBIDDEN message: Insufficient access to organization request_id: req_example '404': description: The resource does not exist, or your organization cannot access it. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: code: RESOURCE_NOT_FOUND message: Resource not found request_id: req_example '409': description: >- The current state of the resource or an accounting rule prevents this operation. Read the resource again before you choose another action. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: code: CONFLICT message: The resource state does not allow this operation. request_id: req_example '429': description: >- Too many requests. If the response has a `Retry-After` header, wait that many seconds before you retry. Otherwise, read `error.message`. headers: Retry-After: description: Seconds to wait before retrying. schema: type: integer minimum: 1 content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: code: RATE_LIMITED message: Rate limit exceeded. Retry after 30s. request_id: req_example '500': description: >- An unexpected error occurred. A write can still have taken effect; check the resource before you retry. Give the `request_id` to support. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: code: INTERNAL_ERROR message: Internal server error request_id: req_example '503': description: >- A service that this operation needs is unavailable. If the response has a `Retry-After` header, wait that many seconds. Check for earlier accepted work before you send the request again. headers: Retry-After: description: Seconds to wait before retrying. schema: type: integer minimum: 1 content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: code: SERVICE_UNAVAILABLE message: Service unavailable. request_id: req_example components: schemas: ErrorResponse: type: object required: - error properties: error: type: object required: - code - message - request_id properties: code: type: string description: Machine-readable error code. message: type: string description: Technical description for developers. fields: type: object additionalProperties: type: string description: >- Present only on VALIDATION_ERROR. Maps failing field paths to reason strings. details: type: object additionalProperties: true description: >- Optional redacted diagnostic details. Request validation uses fields or field_errors. suggested_action: type: string description: A suggested next step. documentation_url: type: string format: uri description: Link to documentation about this error. request_id: type: string description: Unique request ID for support escalation. description: Error details. securitySchemes: ApiKey: type: apiKey in: header name: X-API-Key description: >- Your organization API key. Some operations also need a key that is associated with a user; their pages say so. ````