> ## Documentation Index > Fetch the complete documentation index at: https://docs.dimepayments.com/llms.txt > Use this file to discover all available pages before exploring further. # List Documents > The documents held for a merchant, so you can confirm what we have received. Covers documents uploaded through this API and those added by our team or through the merchant application. ## OpenAPI ````yaml https://app.dimepayments.com/openapi.yaml get /api/document/list openapi: 3.0.3 info: title: Dime Payments API Documentation description: >- A simple, basic API for managing Merchants through Dime Payments. JSON based REST API version: 1.0.0 servers: - url: https://app.dimepayments.com security: - default: [] tags: - name: Merchant management description: '' - name: Transaction management description: >- APIs for managing transactions. Depending on API KEY permissions, one should be able to charge credit cards, ACH, Google/Apple Pay wallets along with other functions. - name: Chargeback management description: '' - name: Document management description: '' - name: Addresses description: |- APIs for managing customer addresses - name: Customer management description: >- APIs for managing customers. Depending on API KEY permissions, one should be able to list, create, update, and delete customers along with several other customer specific requests. - name: Deposit management description: '' - name: Held funds description: '' - name: Invoice management description: >- APIs for managing invoices. Depending on API KEY permissions, one should be able to list, create, update, delete, and send invoices, manage their line items, and manage recurring-invoice schedules. Every request is scoped to a single Merchant via the required `data.sid`. - name: Payment Method management description: >- APIs for managing payment methods associated with customers. Depending on API KEY permissions, one should be able to list, show, create, update, and delete payment methods. - name: Recurring Payments management description: >- APIs for managing recurring payments. Depending on API KEY permissions, one should be able to create, edit, pause, cancel along with other functions. - name: Subscription Plans management description: >- Merchant-facing API for subscription plans (recurring offerings customers subscribe to). The merchant is identified by `data.sid`; the token must carry the matching `subscription-plan:*` ability. Mirrors the recurring-payment and invoice API controllers. - name: Subscriptions management description: >- Merchant-facing API for individual customer subscriptions (enrollments in a plan). The merchant is identified by `data.sid`; the token must carry the matching `subscription:*` ability. Lifecycle transitions delegate to the {@see \App\Actions\Subscription} action classes so the matching `SUBSCRIPTION_*` webhook always fires. Mirrors the recurring-payment and subscription-plan API controllers. - name: Zapier description: >- APIs for use through Zapier. Depending on API KEY permissions, one should be able to see customers and transactions data. paths: /api/document/list: get: tags: - Document management summary: List Documents description: |- The documents held for a merchant, so you can confirm what we have received. Covers documents uploaded through this API and those added by our team or through the merchant application. operationId: listDocuments parameters: [] requestBody: required: false content: application/json: schema: type: object properties: data: type: object description: '' example: [] properties: sid: type: string description: The ID of the merchant. example: '91828382' required: - sid filters: type: object description: '' example: [] properties: doc_type: type: string description: Only documents of this type. example: RetrievalRequest chargeback_transaction_info_id: type: string description: Only documents attached to this chargeback. example: '"8675309"' responses: '200': description: Found content: application/json: schema: type: object example: data: - uuid: 9b1c... file_name: receipt.pdf doc_type: RetrievalRequest chargeback_transaction_info_id: '8675309' size: 20841 uploaded_at: '2026-09-18T11:35:01+00:00' uploaded_via: api sent_to_processor: null properties: data: type: array example: - uuid: 9b1c... file_name: receipt.pdf doc_type: RetrievalRequest chargeback_transaction_info_id: '8675309' size: 20841 uploaded_at: '2026-09-18T11:35:01+00:00' uploaded_via: api sent_to_processor: null items: type: object properties: uuid: type: string example: 9b1c... file_name: type: string example: receipt.pdf doc_type: type: string example: RetrievalRequest chargeback_transaction_info_id: type: string example: '8675309' size: type: integer example: 20841 uploaded_at: type: string example: '2026-09-18T11:35:01+00:00' uploaded_via: type: string example: api sent_to_processor: type: string example: null nullable: true '401': description: Incorrect API Key Permission content: application/json: schema: type: object example: data: message: Permission Denied. properties: data: type: object properties: message: type: string example: Permission Denied. '404': description: '' content: application/json: schema: oneOf: - description: Unknown merchant type: object example: data: message: No such Merchant properties: data: type: object properties: message: type: string example: No such Merchant - description: No documents found type: object example: data: message: No documents found properties: data: type: object properties: message: type: string example: No documents found components: securitySchemes: default: type: http scheme: bearer description: >- You can retrieve your token by visiting your dashboard and clicking Generate API token under your profile in top right. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.