> ## Documentation Index > Fetch the complete documentation index at: https://docs.dintero.com/llms.txt > Use this file to discover all available pages before exploring further. # Generate a test settlement report > Generate a test settlement report. Only available in test. *scopes*: - admin:billing - admin:reports ## OpenAPI ````yaml /mintlify-docs/openapi/spec-payments-v2.yaml post /accounts/{aid}/settlements/reports/generate-test-report openapi: 3.0.0 info: title: Payments API v2 contact: name: API Integration Support email: integration@dintero.com description: | Public endpoints for payments served under the account-scoped URL format `https://api.dintero.com/v1/accounts/{aid}/...`. version: LATEST license: name: UNLICENSED url: https://dintero.com x-logo: url: https://docs.dintero.com/img/dintero-dark-padded.svg altText: Dintero Logo servers: - url: https://api.dintero.com/v1 security: - JWT: [] tags: - name: Transactions x-displayName: Transactions description: | View and perform operations on transactions - name: session x-displayName: Sessions description: | A Checkout Session relates to an order in your system. When an order has been placed you create a corresponding Checkout Session to receive payment for that order. - name: payment x-displayName: Payment description: | Resources used by the customer aka user to complete the payment of a session. - name: settlements x-displayName: Settlement reports description: Get settlement reports generated per payout - name: settlements.configuration x-displayName: Configuration description: Configure settlement reports - name: reports x-displayName: Reports description: List the generated monthly transaction reports - name: Sellers x-displayName: Sellers description: Manage the signup of a new Seller / Merchant account - name: example-session-callbacks x-displayName: Example Callbacks description: Example of callbacks delivered - name: v2-config-payout-destinations x-displayName: Sellers description: Get payout data for sellers - name: Card Tokens description: | Manage card tokens - name: terminals x-displayName: Terminals description: Terminal operations - name: v2-fund-transfers x-displayName: Fund transfers description: Transfer funds between sellers - name: payout-destinations x-displayName: payout destinations description: | Payout destinations - name: account-stores x-displayName: stores description: | Manage account stores - name: account-terminals x-displayName: terminals description: | Manage account terminals - name: report-configuration x-displayName: Report configuration description: Manage report configurations - name: kpi x-displayName: KPI description: Get KPI data paths: /accounts/{aid}/settlements/reports/generate-test-report: post: tags: - settlements summary: aid_settlement_generate_test_report description: | Generate a test settlement report. Only available in test. *scopes*: - admin:billing - admin:reports operationId: aid_settlement_generate_test_report parameters: - $ref: '#/components/parameters/accountId' requestBody: content: application/json: schema: $ref: '#/components/schemas/TestReportOptions' responses: '200': description: | No transactions to generate report. This can be if there are no new transaction events to generate report for. content: application/json: schema: $ref: '#/components/schemas/TestReportResponse' '201': description: Settlement report created content: application/json: schema: $ref: '#/components/schemas/TestReportResponse' '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '500': $ref: '#/components/responses/ServerError' servers: - url: https://api.dintero.com/v1 components: parameters: accountId: name: aid description: | An id that uniquely identifies the account. in: path required: true schema: type: string format: ^[PT]{1}\d{8}$ minLength: 9 maxLength: 9 schemas: TestReportOptions: type: object description: > Options to determine which transactions to include. If no options are included transactions from the last 7 days will be included. Only operations for a transaction that has not already been settled will be included. properties: transaction_ids: description: > Array of transaction IDs to include in the report. If a transaction has already been settled earlier it will be ignored. An empty array will be ignored. Should not be combined with `number_of_transactions` or `date_range`. type: array maxItems: 1000 example: - T12345678.aaaabbbbccccddddeeee01 - T12345678.aaaabbbbccccddddeeee02 items: type: string number_of_transactions: description: > Number of transactions to include. Can be combined with `date_range`, but should not be combined with `transaction_ids`. Must be a positive integer. type: integer minimum: 1 maximum: 10000 example: 10 date_range: description: > A date range to limit which transactions to include. Can be combined with `number_of_transactions`, but should not be combined with `transaction_ids`. `start_date` must be before `end_date`. type: object required: - start_date - end_date properties: start_date: type: string format: date example: '2025-12-01' end_date: type: string format: date example: '2025-12-07' TestReportResponse: type: object required: - message properties: message: type: string Error: type: object required: - error properties: error: type: object required: - message properties: code: type: string description: The code used to identify the error/warning errors: type: array description: The nested error(s) encountered during validation items: type: object message: type: string description: The human readable description of the error/warning responses: BadRequest: description: Bad / Invalid request content: application/json: schema: $ref: '#/components/schemas/Error' Unauthorized: description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/Error' Forbidden: description: Forbidden content: application/json: schema: $ref: '#/components/schemas/Error' ServerError: description: Unexpected Error content: application/json: schema: $ref: '#/components/schemas/Error' securitySchemes: JWT: type: http description: > Bearer authentication (token authentication) should be used for accessing the API. Use [Get Token](/api-reference/authenticate/aid_auths_oauth_token_post) to get an access token for client credentials. Pass the token in the request header: Authorization: Bearer {access_token} where the **access_token** is JSON Web Tokens (JWT). scheme: bearer bearerFormat: JWT ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.