> ## Documentation Index > Fetch the complete documentation index at: https://docs.dakota.xyz/llms.txt > Use this file to discover all available pages before exploring further. # Answer a request for information > Records the applicant's response to a request for information and hands the application back to the reviewer: `rfi_status` becomes `information_received` and `customer.rfi.responded` is raised. Call it after uploading whatever the reviewer asked for. The uploads are already attached to the application, so a request for documents alone needs no body beyond `{}`. `answers` carries the reviewer's free-text questions; `document_ids` inside an entry ties uploaded documents to that particular answer. It answers the reviewer's request only, so unlike submitting the application again it does not require the rest of the application to be complete. It does not verify that a request is outstanding: on an application with no open request it still moves the status and raises the event. **Authentication:** Application Token (X-Application-Token header). The token is the `token` query parameter of the customer's `resubmit_url`, which `GET /customers/{customer_id}` returns while a request with a resubmission scope is open. A request sent without one has no `resubmit_url`; take the token from `application_url` instead. ## OpenAPI ````yaml /openapi.yaml post /applications/{id}/rfi/resubmit openapi: 3.0.3 info: title: Dakota Platform API version: 1.0.0 description: >- Combined API specification for Dakota Platform services: - Issuance API: Asset minting and burning operations - Onboarding API: Know Your Business/Customer verification - On/Off Ramp API: Managing on-ramp and off-ramp accounts - Recipients API: Managing destinations for KYB'd entities - Transactions API: Viewing transaction history across platform operations ## Authentication and API Headers All API endpoints require the following headers: - `X-Idempotency-Key`: Required for all POST endpoints to ensure request idempotency - `x-api-key`: Required for authentication across all endpoints Note: On /applications endpoints you need a token for authentication instead of a x-api-key - `x-application-token`: Required for authentication on public /applications endpoints (alternative to `x-api-key` where documented) ## Rate Limits Requests are rate limited per API key. Every response includes the following headers: | Header | Description | | --- | --- | | `X-RateLimit-Limit` | Maximum requests allowed in the current one-minute window. | | `X-RateLimit-Remaining` | Requests remaining in the current window. | | `X-RateLimit-Reset` | Absolute Unix timestamp (seconds since epoch) when the current rate-limit window resets. | When a request is throttled (`429`), responses also include `Retry-After` with seconds to wait before retrying. servers: - url: https://api.platform.dakota.xyz description: Production environment - url: https://api.platform.sandbox.dakota.xyz description: Sandbox — safe for testing with simulated data security: - ApiKeyAuth: [] tags: - name: Agentic Payments x-beta: true description: >- Beta — agent-driven payments: provision agents, draft and approve spending mandates, accept reviewed instructions, and manage scheduled payments. **Prerequisites:** Customer onboarded; signer groups attached for recognition. **Related:** Wallets, Signer Groups, Transactions - name: Mandates x-beta: true description: >- Beta — spending mandates: signed, signer-bound authorizations governing what may be spent, approved or cancelled by a second recognized signer (§8 — the dual-control rule that every mandate mutation must be signed by a recognized signer OTHER than the bound one). Independent of agents and scheduled payments. **Prerequisites:** Signer groups attached for recognition. **Related:** Signer Groups, Transactions - name: Insights x-beta: true description: >- Beta — read-only insight: a deterministic report over a customer's agentic activity (funding balances, upcoming obligations, failures, mandate headroom and expiry), or — via `GET /insights` — over the whole client's book, with portfolio KPIs, daily series and a per-customer roll-up. Never moves money, never creates or changes anything. **Prerequisites:** Customer onboarded; insight is computed from the customer's scheduled payments, mandates, and wallets. **Related:** Agentic Payments, Mandates - name: Customers description: >- Manage customer entities representing businesses and organizations onboarded to Dakota. **Prerequisites:** Complete KYB via Onboarding endpoints before initiating money movement. **Related:** Onboarding, Recipients, Transactions, Accounts, Wallets - name: Wallets description: >- Manage wallets, balances, and wallet-to-signer-group relationships for custody and movement controls. **Prerequisites:** Customer must exist. Configure signer groups before policy-enforced workflows. **Related:** Signer Groups, Policies, Transactions, Customers - name: Transactions description: >- Create, cancel, and retrieve transaction records across account and wallet flows. **Prerequisites:** Accounts or destinations must be configured based on flow type. **Related:** Accounts, Recipients, Policies, Events - name: Recipients description: >- Manage recipient entities and destination rails used by customers for payouts and transfers. **Prerequisites:** Customer must be onboarded and active. **Related:** Customers, Transactions, Accounts, Onboarding - name: Accounts description: >- Manage account resources used for onramp, offramp, and swap operations. **Prerequisites:** Customer must be created and network/asset constraints must be known. **Related:** Customers, Transactions, Auto Transactions, Info - name: Auto Transactions description: >- Manage automated transaction configurations and execution history for account automation workflows. **Prerequisites:** Source account must exist and be configured for automation. **Related:** Accounts, Transactions, Events - name: Onboarding description: >- Manage KYB/KYC onboarding lifecycle, application documents, attestations, and verification steps. **Prerequisites:** Customer context and required entity/application metadata. **Related:** Customers, Exceptions, Recipients, Transactions - name: Policies description: >- Define and manage policy objects and rules used for transaction governance and risk controls. **Prerequisites:** Wallet and signer group resources should be configured for enforcement scenarios. **Related:** Wallets, Signer Groups, Transactions - name: Signer Groups description: >- Manage signer groups and signer assignments for multi-party authorization models. **Prerequisites:** Wallets should exist before linking signer groups. **Related:** Wallets, Policies, Transactions - name: Authentication description: >- Manage API authentication credentials and key lifecycle for platform access. **Prerequisites:** Client organization must be provisioned. **Related:** Users, Info - name: Users description: >- Manage client users, roles, and identity metadata for platform access control. **Prerequisites:** Auth credentials and client context must be established. **Related:** Authentication - name: Webhooks description: >- Manage outbound webhook targets and delivery configuration for event notifications. **Prerequisites:** Subscriber endpoint must be reachable and secured. **Related:** Events, Authentication - name: Payouts description: >- Manage where Dakota sends your accrued developer-fee payouts. **Prerequisites:** Auth credentials and client context must be established. **Related:** Events - name: RD Marketing Fee description: >- Everything behind your RD marketing fee: read what a month came to, declare the wallets you hold outside Dakota so the RD in them counts, and say where the fee should be sent. **Prerequisites:** Client must be in the RD marketing-fee programme. A month is readable once it has closed. **Related:** Wallets, Events - name: Self Serve description: >- Buy and track prepaid credits, and read the tiers and pricing they are sold at. **Prerequisites:** Auth credentials and client context must be established. **Related:** Billing - name: Events description: >- Retrieve event records emitted by platform operations for audit and troubleshooting. **Prerequisites:** Requesting client must have access to referenced resources. **Related:** Webhooks, Transactions, Onboarding - name: Info description: >- Read platform capability metadata, such as supported rails, networks, and assets. These operations are served under `/capabilities/*` - `GET /capabilities/countries` and `GET /capabilities/networks`. The tag name does not appear in the request paths. **Prerequisites:** Valid authentication headers. **Related:** Accounts, Transactions - name: Sandbox description: >- Trigger sandbox-only simulation endpoints for safe end-to-end integration testing with synthetic data. The sandbox host (`https://api.platform.sandbox.dakota.xyz`) also accepts a family of `X-Sandbox-*` request headers on most write endpoints (`Customers`, `Accounts`, `Transactions`, simulate endpoints) that let integrators drive deterministic failure modes — pick a preset via `X-Sandbox-Scenario`, or compose a custom one with `X-Sandbox-Error-Step`/`X-Sandbox-Error-Status`/`X-Sandbox-Error-Message`. `X-Sandbox-Instant-Completion` collapses async flows to a single synchronous step, and `X-Sandbox-Skip-Auto-Approval` keeps newly created KYB applications in `pending` for manual-review testing. All `X-Sandbox-*` headers are ignored in production. **Prerequisites:** Sandbox environment and test customer data. **Related:** Customers, Accounts, Transactions, Onboarding - name: Legal description: |- The legal documents customers accept — terms of service, privacy policy, e-sign notice, and partner agreements. Dakota publishes these here, and this is the authoritative source: the hosted onboarding flow, the dakota.xyz website, and your own integration all read the same revisions. Present the current revision to your customer before capturing their acceptance so the record reflects the text they actually saw. paths: /applications/{id}/rfi/resubmit: post: tags: - Onboarding - RFI summary: Answer a request for information description: | Records the applicant's response to a request for information and hands the application back to the reviewer: `rfi_status` becomes `information_received` and `customer.rfi.responded` is raised. Call it after uploading whatever the reviewer asked for. The uploads are already attached to the application, so a request for documents alone needs no body beyond `{}`. `answers` carries the reviewer's free-text questions; `document_ids` inside an entry ties uploaded documents to that particular answer. It answers the reviewer's request only, so unlike submitting the application again it does not require the rest of the application to be complete. It does not verify that a request is outstanding: on an application with no open request it still moves the status and raises the event. **Authentication:** Application Token (X-Application-Token header). The token is the `token` query parameter of the customer's `resubmit_url`, which `GET /customers/{customer_id}` returns while a request with a resubmission scope is open. A request sent without one has no `resubmit_url`; take the token from `application_url` instead. operationId: RFIResubmit parameters: - name: id in: path required: true schema: type: string - name: x-idempotency-key in: header required: false description: | Unique key, a UUID. The server rejects this call with 400 when the header is absent or is not a UUID, so send one on every request. A repeat of the same key within the cache window returns the original response instead of recording the answers again. schema: type: string format: uuid requestBody: required: false content: application/json: schema: type: object properties: answers: type: array description: >- Applicant answers to the freeform RFI questions asked on this application. items: type: object required: - question_key - answer_text properties: question_key: type: string description: | The `key` of the RFI question being answered. Stored truncated to the first 200 characters. prompt: type: string description: | Snapshot of the question text, stored for display. Stored truncated to the first 20000 characters. answer_text: type: string description: | The applicant's free-text answer. Stored truncated to the first 20000 characters. document_ids: type: array description: | Optional ids of documents the applicant attached with this answer, as returned by the upload endpoints. An id that belongs to another application is dropped silently: the call still returns 200 and the answer is stored without it, so check the ids you send. items: type: string example: answers: - question_key: source_of_wealth prompt: Please explain how the funds were accumulated. answer_text: >- Proceeds from the 2024 sale of the founder's previous company. document_ids: - 1NFHrqBHb3cTfLVkFSGmHZqdDPi responses: '200': description: | The response was recorded and the application is back with the reviewer. Each call records the `answers` it carries, so a second call with a NEW `x-idempotency-key` leaves the reviewer reading the same answer twice. The status change and `customer.rfi.responded` are raised once either way. Retry with the SAME `x-idempotency-key` as the call you are retrying: within the cache window the original response is replayed and nothing is recorded again, which is what makes a retry safe when you cannot tell whether the first attempt arrived. '400': description: | The `x-idempotency-key` header is missing or is not a UUID, or the request carries no body at all. A body is always read, so send `{}` when there are no answers to record. content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' example: type: https://docs.dakota.xyz/api-reference/errors#invalid-request title: Invalid Request status: 400 detail: Missing required X-Idempotency-Key header instance: /applications/31TgwCp3sMdF9gY4nT6hKvXqRbLm/rfi/resubmit request_id: req_7f3a8b2c '401': description: No application token was supplied. content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' example: type: >- https://docs.dakota.xyz/api-reference/errors#authentication-error title: Authentication Required status: 401 detail: Missing X-Application-Token header instance: /applications/31TgwCp3sMdF9gY4nT6hKvXqRbLm/rfi/resubmit request_id: req_7f3a8b2c '403': description: | The application token is invalid or expired, or belongs to a different application. An API key is also refused here. Application routes accept a client API key only from Dakota's own internal users, so a client calling this route with the key it uses everywhere else gets this status, not a 401. Use the application token. content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' example: type: https://docs.dakota.xyz/api-reference/errors#forbidden title: Forbidden status: 403 detail: Invalid request or expired token instance: /applications/31TgwCp3sMdF9gY4nT6hKvXqRbLm/rfi/resubmit request_id: req_7f3a8b2c '404': description: Application not found content: application/json: schema: $ref: '#/components/schemas/Error' example: code: application_not_found message: Application not found '409': description: >- The application has already been decided; the resubmission window is closed content: application/json: schema: $ref: '#/components/schemas/Error' example: code: invalid_request message: >- The application has already been decided; the resubmission window is closed security: - ApplicationTokenAuth: [] components: schemas: ProblemDetails: type: object required: - type - title - status description: | Error response following RFC 9457 Problem Details. Public API error responses use this format. example: type: https://docs.dakota.xyz/api-reference/errors#not-found title: Customer Not Found status: 404 detail: Customer cst_2abc123 was not found in your organization. instance: https://api.platform.dakota.xyz/customers/cst_2abc123 request_id: req_7f3a8b2c properties: type: type: string format: uri description: | URI reference identifying the problem type. Resolves to human-readable documentation. example: https://docs.dakota.xyz/api-reference/errors#not-found title: type: string description: >- Short, human-readable summary of the problem type. Stable across occurrences. example: Customer Not Found status: type: integer description: HTTP status code for this occurrence. example: 404 detail: type: string description: Human-readable explanation specific to this occurrence. example: Customer cst_2abc123 was not found in your organization. instance: type: string format: uri description: The request path that triggered this error. example: https://api.platform.dakota.xyz/customers/cst_2abc123 request_id: type: string description: Unique request identifier. Include when contacting support. example: req_7f3a8b2c errors: type: array description: Field-level validation errors (present for validation failures). items: $ref: '#/components/schemas/ValidationError' resolution_url: type: string format: uri description: | A link the customer can follow to CLEAR this error, present only on problems with a concrete self-service remedy. Today this is returned by `#terms-not-accepted`, where it points at the hosted flow in which the outstanding agreement can be signed. The link is token-gated and usable as-is — send the customer to it directly rather than parsing it out of `detail`. example: >- https://onboarding.dakota.xyz/applications/2abc123?token=tok_7f3a8b2c user_message: type: string description: | A plain-language rendition of `detail` written for the end customer, present when one exists for this error. `detail` names request fields and actions so a machine caller (such as a payment agent drafting proposals) can self-correct; `user_message` says the same thing without API vocabulary. Clients that relay errors into a human surface (chat, email, UI) should show `user_message` when present and fall back to `detail`. example: >- ACH payments pay out USD, so a USDC payout isn't possible on this rail. Change the payout currency to USD and try again. Error: type: object required: - code - message properties: code: type: string description: Machine-readable error code message: type: string description: Human-readable error message details: type: object description: Optional metadata for troubleshooting additionalProperties: true ValidationError: type: object required: - field - message properties: field: type: string description: Field path using dot notation for nested fields. example: bank_account.routing_number message: type: string description: Human-readable description of the field error. example: Routing number must be exactly 9 digits code: type: string description: Machine-readable error code for this field. example: invalid_format securitySchemes: ApiKeyAuth: type: apiKey in: header name: x-api-key ApplicationTokenAuth: type: apiKey in: header name: X-Application-Token description: > Application-specific token for public URL access. Generated when a customer is created. Provides access to a single application without requiring an API key. Token is valid for 90 days and rate-limited to 250 requests per hour. ````