> ## 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. # List all onboarding applications > Returns a paginated list of your onboarding applications for both businesses and individuals. Use the `type` parameter to filter by application type, and `status` to filter by application status. Supports cursor-based pagination using `starting_after`, `ending_before`, and `limit` parameters. **Authentication:** Accepts API Key (X-API-Key header). ## OpenAPI ````yaml /openapi.yaml get /applications 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-alpha: true description: >- Alpha — 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-alpha: true description: >- Alpha — 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-alpha: true description: >- Alpha — read-only account insight: a deterministic report over a customer's agentic activity (funding balances, upcoming obligations, failures, mandate headroom and expiry) plus an advisory chat that narrates it. 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: 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. **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 paths: /applications: get: tags: - Onboarding summary: List all onboarding applications description: > Returns a paginated list of your onboarding applications for both businesses and individuals. Use the `type` parameter to filter by application type, and `status` to filter by application status. Supports cursor-based pagination using `starting_after`, `ending_before`, and `limit` parameters. **Authentication:** Accepts API Key (X-API-Key header). operationId: listApplications parameters: - name: type in: query required: false description: Filter by application type schema: type: string enum: - business - individual - name: status in: query required: false description: Filter by application status schema: type: string enum: - pending - submitted - completed - $ref: '#/components/parameters/StartingAfterParam' - $ref: '#/components/parameters/EndingBeforeParam' - $ref: '#/components/parameters/LimitParam' responses: '200': description: List of applications content: application/json: schema: type: object required: - data - meta properties: data: type: array items: $ref: '#/components/schemas/ApplicationListItem' meta: $ref: '#/components/schemas/Meta' example: data: - application_id: 2hCjxJzUAW6JVRkZqaF9E0KpM3a application_type: business application_status: pending application_decision: approved business: id: 2hCjxJzUAW6JVRkZqaF9E0KpM3a legal_name: Acme Corp individuals: - id: 2hCjxJzUAW6JVRkZqaF9E0KpM3b first_name: John last_name: Doe edd_id: 2hCjxJzUAW6JVRkZqaF9E0KpM3c created_at: '2024-01-15T10:30:00Z' updated_at: '2024-01-15T14:45:00Z' submitted_at: '2024-01-15T16:00:00Z' risk_rating: score: 7 num_factors: 4 percentage: 62.5 level: high factors: - name: country_risk value: 3 level: high input: US description: Country risk based on incorporation country reason: United States is a low-risk jurisdiction prohibited: false edd_required: true prohibited: false prohibited_reason: Sanctioned country version: v1 data_version: '2026-01-07' config: threshold_low: 25 threshold_high: 50 calculated_at: '2024-01-15T10:30:00Z' meta: total_count: 100 has_more_after: true has_more_before: false '400': description: Invalid request 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: Invalid request instance: https://api.platform.dakota.xyz/applications request_id: req_01hzy6y7v8w9x0y1z2a3b4c5d6 '401': description: Unauthorized content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' example: type: >- https://docs.dakota.xyz/api-reference/errors#authentication-error title: Unauthorized status: 401 detail: Unauthorized instance: https://api.platform.dakota.xyz/applications request_id: req_01hzy6y7v8w9x0y1z2a3b4c5d6 '403': description: Forbidden content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' example: type: https://docs.dakota.xyz/api-reference/errors#forbidden title: Forbidden status: 403 detail: Forbidden instance: https://api.platform.dakota.xyz/applications request_id: req_01hzy6y7v8w9x0y1z2a3b4c5d6 default: description: Unexpected error content: application/problem+json: schema: $ref: '#/components/schemas/ProblemDetails' example: type: https://docs.dakota.xyz/api-reference/errors#internal-error title: Unexpected error status: 500 detail: Unexpected error instance: https://api.platform.dakota.xyz/applications request_id: req_01hzy6y7v8w9x0y1z2a3b4c5d6 externalDocs: description: Read full guide in docs url: >- https://docs.dakota.xyz/api-reference/onboarding/list-all-onboarding-applications components: parameters: StartingAfterParam: name: starting_after in: query required: false description: >- A cursor for use in pagination. `starting_after` is a KSUID for the object you are listing that defines your place in the list. For instance, if you make a list request and receive 100 objects, ending with ID `2B5J8KZ9N7M1K3P6Q8R4T7V9`, your subsequent call can include `starting_after=2B5J8KZ9N7M1K3P6Q8R4T7V9` in order to fetch the next page of the list. schema: $ref: '#/components/schemas/KSUID' EndingBeforeParam: name: ending_before in: query required: false description: >- A cursor for use in pagination. `ending_before` is a KSUID for the object you are listing that defines your place in the list. For instance, if you make a list request and receive 100 objects, starting with ID `2B5J8KZ9N7M1K3P6Q8R4T7V9`, your subsequent call can include `ending_before=2B5J8KZ9N7M1K3P6Q8R4T7V9` in order to fetch the previous page of the list. schema: $ref: '#/components/schemas/KSUID' LimitParam: name: limit in: query required: false description: >- A limit on the number of objects to be returned. Limit can range between 1 and 100, and the default is 20. schema: type: integer minimum: 1 maximum: 100 default: 20 schemas: ApplicationListItem: type: object description: >- Lightweight application item for list views - no PII, just IDs, names, and timestamps required: - application_id - application_type - application_status - individuals - created_at - updated_at properties: application_id: type: string format: ksuid description: Unique application identifier example: 2hCjxJzUAW6JVRkZqaF9E0KpM3a application_type: type: string description: Type of application enum: - business - individual example: business application_status: $ref: '#/components/schemas/ApplicationStatus' application_decision: type: string description: Application decision status (if a decision has been made) enum: - approved - declined - auto_declined - withdrawn example: approved business: $ref: '#/components/schemas/BusinessListItem' description: Business entity (only present for business applications) individuals: type: array description: Individual entities associated with this application items: $ref: '#/components/schemas/IndividualListItem' edd_id: type: string format: ksuid description: EDD record ID (if exists) example: 2hCjxJzUAW6JVRkZqaF9E0KpM3c created_at: type: string format: date-time description: When the application was created example: '2024-01-15T10:30:00Z' updated_at: type: string format: date-time description: When the application was last updated example: '2024-01-15T14:45:00Z' submitted_at: type: string format: date-time description: When the application was submitted (if submitted) example: '2024-01-15T16:00:00Z' risk_rating: $ref: '#/components/schemas/RiskRating' description: Risk rating information (only present for superadmin users) Meta: type: object description: Meta information about the response required: - total_count - has_more_after - has_more_before properties: total_count: type: integer description: Total number of items available example: 100 has_more_after: type: boolean description: Indicates whether there are more items that follow this set. example: true has_more_before: type: boolean description: Indicates whether there are more items that precede this set. example: false 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' KSUID: type: string title: KSUID description: >- KSUID is a 27-character globally unique ID that combines a timestamp with a random component. Used for all entity identifiers in the Dakota platform. pattern: ^[0-9A-Za-z]{27}$ minLength: 27 maxLength: 27 example: 1NFHrqBHb3cTfLVkFSGmHZqdDPi ApplicationStatus: type: string title: Application Status description: > Current status of an application in the onboarding flow. Status flow: - `pending` - Initial state, not yet submitted - `submitted` - Submitted for verification - `under_review` - Being reviewed by compliance team - `request_for_information` - Admin requesting additional info/documents from applicant - `admin_revision` - Admin making corrections to application data - `approved` - Application approved - `declined` - Application declined - `completed` - Legacy status (deprecated, use approved/declined instead) - `compliance_review` - Application is awaiting compliance review of a Proof of Address document. Set when an individual applicant uploads a PoA-equivalent document (proof_of_address, bank_statement, or utility_bill) after their application has already been approved or completed. The customer remains active but is subject to the $3,000 USD-equivalent rolling 7-day transaction limit until the review concludes. enum: - pending - submitted - under_review - request_for_information - admin_revision - approved - declined - completed - compliance_review example: submitted BusinessListItem: type: object description: Lightweight business info for list views required: - id - legal_name properties: id: type: string format: ksuid example: 2hCjxJzUAW6JVRkZqaF9E0KpM3a legal_name: type: string description: Legal business name example: Acme Corp IndividualListItem: type: object description: Lightweight individual info for list views required: - id - first_name - last_name properties: id: type: string format: ksuid example: 2hCjxJzUAW6JVRkZqaF9E0KpM3b first_name: type: string description: First name example: John last_name: type: string description: Last name example: Doe RiskRating: type: object description: Risk rating assessment for an application required: - score - num_factors - percentage - level - factors - edd_required - prohibited - version - calculated_at - data_version - config properties: score: type: integer description: Sum of all factor values example: 7 num_factors: type: integer description: Number of factors evaluated example: 4 percentage: type: number format: double description: Risk percentage (0-100) example: 62.5 level: type: string description: Risk level classification enum: - low - medium - high example: high factors: type: array description: Detailed breakdown of risk factors items: type: object required: - name - value - level - input - description - reason - prohibited properties: name: type: string description: Factor name (e.g., 'country_risk', 'industry_risk') example: country_risk value: type: integer description: Risk factor value (1=low, 2=medium, 3=high) enum: - 1 - 2 - 3 example: 3 level: type: string description: Risk level for this factor enum: - low - medium - high example: high input: type: string description: Actual input value (country code, NAICS, etc.) example: US description: type: string description: Human-readable description of the factor example: Country risk based on incorporation country reason: type: string description: Explanation for this risk level example: United States is a low-risk jurisdiction prohibited: type: boolean description: Whether this factor value is prohibited example: false edd_required: type: boolean description: Whether Enhanced Due Diligence is required (true if level is high) example: true prohibited: type: boolean description: >- Whether this entity is prohibited from onboarding (true if any factor is prohibited) example: false prohibited_reason: type: string description: Reason for prohibition if prohibited is true example: Sanctioned country version: type: string description: Risk rating calculation version example: v1 data_version: type: string description: Risk data version (which CSV files were used) example: '2026-01-07' config: $ref: '#/components/schemas/RiskConfig' calculated_at: type: string format: date-time description: When the risk rating was calculated example: '2024-01-15T10:30:00Z' 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 RiskConfig: type: object description: Configuration parameters used during risk calculation required: - threshold_low - threshold_high properties: threshold_low: type: number format: double description: Low to medium risk threshold percentage example: 25 threshold_high: type: number format: double description: Medium to high risk threshold percentage example: 50 securitySchemes: ApiKeyAuth: type: apiKey in: header name: x-api-key ````