> ## Documentation Index > Fetch the complete documentation index at: https://developers-sandbox.uqpaytech.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Create Report > Creates a report for account transactions, card transactions or transaction settlements. ## OpenAPI ````yaml /card-issuance/v1.6/issuing.yaml post /v1/issuing/reports openapi: 3.0.2 info: title: Issuing API version: 0.0.1 description: > UQPAY Issuing API allows you to issue virtual cards, manage cardholders, and monitor card transactions. ## What you can do - Create and manage virtual cards (issue, activate, freeze, cancel) - Onboard and verify cardholders with KYC - Set spending limits and card controls - Recharge and withdraw card balances - Query card transactions and account balances - Transfer funds between issuing accounts - Generate and download reports ## Authentication All requests require a valid auth token obtained via the [Access Token](/account-center/v1.6/api-reference/access-token) endpoint. Include the token in the `x-auth-token` header. ## Idempotency POST requests support the `x-idempotency-key` header to safely retry without creating duplicate resources. contact: name: UQPAY Support Team url: https://www.uqpay.com/support email: support@uqpay.com license: name: Proprietary url: https://www.uqpay.com/legal/api-terms termsOfService: https://www.uqpay.com/legal/terms x-api-id: uqpay-issuing-api-v1.6.0 x-categories: - Card Issuing - Transaction Processing x-features: - Virtual Card Issuance - Real-time Processing - Webhook Notifications - Comprehensive Reporting - Transaction Monitoring servers: - url: https://api-sandbox.uqpaytech.com/api description: Sandbox base URL. - url: https://api.uqpay.com/api description: Production base URL. security: [] tags: - name: Cards description: >- These APIs are designed for you to be able to manage your consumer's cards easily, allowing you to set spending limits, modify the status of the cards. - name: Cardholders description: >- You can create cardholders, which are authorized representatives of your business that can be issued cards. - name: Transactions description: >- These APIs allow you to retrieve information on transactions that are made on your user's cards. - name: Products description: >- With this set of APIs, you will be able to create card orders for your customers. - name: Balances description: >- The available and pending amounts for each currency are broken down further by payment source types. You can retrieve it to see the balance currently on your issuing account. - name: Transfers description: Transfer funds between issuing accounts. - name: Reports description: Generate and download issuing reports. - name: Simulator description: Simulate card transactions on the sandbox environment. paths: /v1/issuing/reports: post: tags: - Reports summary: Create Report description: >- Creates a report for account transactions, card transactions or transaction settlements. operationId: create-report parameters: - $ref: '#/components/parameters/XIdempotencyKey' - $ref: '#/components/parameters/XOnBehalfOf' requestBody: content: application/json: schema: $ref: '#/components/schemas/CreateReportRequest' responses: '200': headers: x-response-id: $ref: '#/components/headers/XResponseId' description: Create report successfully. content: application/json: schema: $ref: '#/components/schemas/CreateReportResponse' title: CreateReportResponse security: - XAuthToken: [] components: parameters: XIdempotencyKey: in: header name: x-idempotency-key schema: type: string format: uuid required: true description: >- A unique identifier (UUID) used to maintain operation idempotency, ensuring that repeated executions of the same operation do not result in unintended effects or duplication. It helps preserve data consistency in the face of network errors, retries, or failures. example: 18523f72-f4de-4f9c-bb8e-ec7d1c4f32be XOnBehalfOf: in: header name: x-on-behalf-of schema: type: string required: false description: > Specifies the sub-account on whose behalf the request is made. This should be set to the `account_id`, which can be retrieved via the [List Connected Accounts](/account-center/v1.6/api-reference/list-connected-accounts) endpoint. If omitted or empty, the request is executed using the master account. More information at [Connected Accounts](/account-center/v1.6/guide/connected-accounts). example: 18523f72-f4de-4f9c-bb8e-ec7d1c4f32be schemas: CreateReportRequest: type: object required: - report_type - start_time - end_time properties: report_type: $ref: '#/components/schemas/ReportType' start_time: $ref: '#/components/schemas/StartTime' end_time: $ref: '#/components/schemas/EndTime' CreateReportResponse: type: object required: - report_id properties: report_id: $ref: '#/components/schemas/ReportId' ReportType: type: string description: >- The type of report file, only `SETTLEMENT` and `LEDGER` can be accepted currently. example: SETTLEMENT StartTime: type: string description: The earliest time for transaction. example: '2024-03-21T17:17:32+08:00' EndTime: type: string description: The latest timestamp for transaction. example: '2024-03-21T17:17:32+08:00' ReportId: type: string example: c0cef051-29c5-4796-b86a-cd5b684bfad7 description: Unique identifier for the report. headers: XResponseId: description: >- Universally unique identifier (UUID v4) for the response. Helpful for identifying a request when communicating with UQPAY support. schema: type: string format: uuid example: 2adba88e-9d63-44bc-b975-9b6ae3440dde securitySchemes: XAuthToken: type: apiKey in: header name: x-auth-token description: The API token for login provided by UQPay. ````