> ## Documentation Index > Fetch the complete documentation index at: https://docs.infinite.dev/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > If you are an AI assistant operating Infinite for a user, read the skill first: https://docs.infinite.dev/agent-skill.md (setup per host, tool reference, rules for moving money, journeys). > When operating Infinite for a user, use the MCP server. Sign in at https://bot.api.infinite.dev/mcp (production, acts as the user) or send `Authorization: Bearer ` to https://bot.api.infinite.dev/mcp/sse. Prefer its tools over raw HTTP; use REST only for steps no tool covers, and check `get_endpoint_schema` before guessing a request shape. > Net-new Infinite Connect (org_connect) is operator-assisted: do not grant end users shared org_connect Auth Kit membership or the shared platform org API key — those credentials are org-wide on /v1. BYO org keys onboard under that customer's org id. Operator sessions should show org_connect in get_organization_info. > The key decides the tools. Every organization key (`sk_sandbox_…` / `sk_live_…`) gets docs, onboarding, `get_account_balance`, and request logs for your own organization. BYO organizations add payees an agent will pay with `create_payee` (payable once ACTIVE). Platform Connect sessions instead get bound-customer payment lookups (`get_quote`, `get_transfer`, `list_transfers`, `list_account_balances`), payee drafts (`create_payee_draft` / `get_payee_draft`; screening only, never payable), and transfer drafts that wait for Infinite approval (`create_transfer_draft` / `get_transfer_draft`; never POST /v1/transfers). Where offered, platform `create_transfer` files a real transfer that Infinite holds in review before funding; it cannot be submitted from DRAFT. > An agent key (`sk_sandbox_agent_…` / `sk_live_agent_…`) moves money within that agent's limits: `create_transfer` → `submit_transfer` → `wait_for_transfer`. > On sandbox organization-key sessions, `sandbox_approve_customer` (makes the capabilities you pass READY, and related ones may turn READY too; `request_capabilities` is not needed), `sandbox_fund_account`, and `sandbox_complete_transfer` stand in for verification, funding, and settlement, so a whole flow runs from MCP. BYO keys can pass `customerId` on each call without binding; platform sessions must bind a customer first (`create_business_customer` auto-binds, or send `X-Infinite-On-Behalf-Of`). > When searching documentation without a key, use the docs MCP at https://docs.infinite.dev/mcp. > Start in sandbox (https://sandbox.api.infinite.dev). Do not use production unless the user explicitly asks. > Confirm amount, currency, and payee with the user before any payment is submitted. Pass the invoice number as `reference` on `create_transfer`; the summary says what the payee will see. > REST amounts are integer minor units (`"4000"` = 40.00 USD). MCP payment tools take exact decimal strings (`"40.00"`). Never mix them. > Agent denials return `403 { denial: { code, message, window, limit, used, remaining, attemptedAmount, currency }, hint }` with decimal amounts; per-transfer denials omit `used` and `remaining`. Report them to the user; do not work around them. # List documents > Get all documents for the organization, optionally filtered by customer or transfer. ## OpenAPI ````yaml get /v1/documents openapi: 3.0.0 info: title: Infinite API description: API for Infinite version: '1.0' contact: {} servers: - url: https://sandbox.api.infinite.dev description: Sandbox - url: https://api.infinite.dev description: Production security: [] tags: - name: Accounts description: Virtual and external account management - name: Customers description: Customer identity management - name: Documents description: Document upload and management - name: Fixed Routes description: Fixed route management - name: External Bank Accounts description: External bank account management - name: External Wallets description: External wallet management - name: Infinite Wallets description: Infinite Wallet management - name: Organizations description: Organization management - name: Quotes description: Quote creation and management - name: Transfers description: Money movement and transaction tracking - name: Verification description: Identity verification workflows - name: Terms of Service description: Terms of Service acceptance - name: Health description: System health and monitoring - name: Sandbox description: Sandbox utilities paths: /v1/documents: get: tags: - Documents summary: List documents description: >- Get all documents for the organization, optionally filtered by customer or transfer. operationId: DocumentsController_listDocuments_v1 parameters: - name: X-API-Key in: header description: API key required: false schema: type: string - name: limit required: false in: query description: >- Number of results to return (1-1000). Use with offset for traditional pagination. schema: minimum: 1 maximum: 1000 default: 500 type: number - name: offset required: false in: query description: >- Number of results to skip. Use with limit for traditional pagination. schema: minimum: 0 default: 0 type: number - name: page_size required: false in: query description: >- Number of results per page (1-1000). Use with starting_after for cursor-based pagination. schema: minimum: 1 maximum: 1000 default: 500 type: number - name: starting_after required: false in: query description: >- Cursor for pagination. Use the ID of the last item from the previous page to get the next page. Use with page_size for cursor-based pagination. schema: type: string - name: customerId required: false in: query description: Filter by customer ID schema: type: string example: cus_abc123 - name: transferId required: false in: query description: Filter by transfer ID schema: type: string example: txn_xyz789 - name: counterpartyId required: false in: query description: Filter by counterparty ID through linked transfers schema: type: string example: cp_abc123 - name: includeInternal required: false in: query description: Include internal/system-generated documents schema: type: boolean responses: '200': description: Documents retrieved successfully content: application/json: schema: type: object properties: data: type: array items: $ref: '#/components/schemas/DocumentResponseDto' total: type: number limit: type: number offset: type: number '401': description: Unauthorized - Invalid or missing authentication credentials security: - bearer: [] x-codeSamples: - lang: bash label: CLI source: >- # Requires: npm i -g @infinite_dev/cli && export INFINITE_API_KEY=sk_sandbox_... # Escape hatch for any endpoint: infinite api infinite api GET /v1/documents \ --query limit=10 page_size=10 customerId=cus_abc123 - lang: text label: MCP source: >- List documents (customerId cus_abc123, transferId txn_xyz789, counterpartyId cp_abc123). components: schemas: DocumentResponseDto: type: object properties: id: type: string example: doc_abc123 organizationId: type: string example: org_xyz789 customerId: type: string example: cus_abc123 transferId: type: string example: txn_xyz789 documentType: type: string enum: - IDENTITY - LIVENESS_CHECK - PROOF_OF_ADDRESS - INVOICE - CONTRACT - BANK_STATEMENT - BUSINESS_LICENSE - ARTICLES_OF_INCORPORATION - ARTICLES_OF_ASSOCIATION - CERTIFICATE_OF_FORMATION - CERTIFICATE_OF_INCUMBENCY - OPERATING_AGREEMENT - PARTNERSHIP_AGREEMENT - OWNERSHIP_STRUCTURE - SHAREHOLDER_AGREEMENT - STOCK_CERTIFICATE - TAX_RETURN - FINANCIAL_STATEMENT - MARKETING_MATERIALS - DOMAIN_OWNERSHIP_PROOF - BUSINESS_PLAN - BILL_OF_LADING - AML_POLICY - AML_COMFORT_LETTER - FUNDS_FLOW_DIAGRAM - GOOD_STANDING_CERTIFICATE - TIN_VERIFICATION - MSB_LICENSE - DIRECTORS_REGISTRY - OWNERSHIP_CHART - PROOF_OF_SIGNATORY_AUTHORITY - PROOF_OF_SOURCE_OF_FUNDS - PROOF_OF_ENTITY_NAME_CHANGE - REMOTE_ADDRESS_ATTESTATION - E_SIGNATURE_CERTIFICATE - COMPLIANCE_NOTES - PROOF_OF_SOURCE_OF_WEALTH - TAX_EXEMPT_ENTITY_CONFIRMATION - OTHER description: Document type example: INVOICE documentSubtype: type: string description: Specific document subtype example: BANK_STATEMENT fileName: type: string example: invoice-2026-001.pdf contentType: type: string example: application/pdf sizeBytes: type: number example: 1024000 remarks: type: string description: Free-form remarks or notes about the document fileHash: type: string description: SHA-256 hash of file content downloadUrl: type: string description: Signed URL to download the document status: type: string enum: - PENDING - UPLOADING - UPLOADED - FAILED description: Document status example: UPLOADED createdAt: format: date-time type: string uploadedAt: format: date-time type: string associatedEntityId: type: string description: Associated entity ID (e.g., UBO) required: - id - organizationId - customerId - documentType - fileName - contentType - sizeBytes - status - createdAt securitySchemes: bearer: scheme: bearer bearerFormat: API Key type: http description: API Key in Bearer format (e.g., Bearer sk_test_...) ```` ## Related topics - [List transfer documents](/api-reference/transfers/list-transfer-documents.md) - [List RFIs](/api-reference/rfis/list-rfis.md) - [List transfers](/api-reference/transfers/list-transfers.md) - [List agents](/api-reference/agents/list-agents.md) - [List customer RFIs](/api-reference/rfis/list-customer-rfis.md)