> ## Documentation Index > Fetch the complete documentation index at: https://v2.docs.conduit.financial/llms.txt > Use this file to discover all available pages before exploring further. # Get an application by ID > Retrieves the full details of a single application. Use this to check the current status of an onboarding or feature request submission. ## OpenAPI ````yaml https://api.sandbox.conduit.financial/v2/api-docs/openapi.json get /applications/{id} openapi: 3.0.0 info: title: Conduit Sandbox API description: >- **Sandbox API** — clients integrate against this surface to exercise happy and unhappy paths without consuming real KYC/PSP credits or moving real money. Customer KYC, banking partners, and crypto custody are stubbed; org-level KYB runs against real providers. Simulation endpoints under `/v2/sandbox/*` drive specific scenarios. Internal and portal endpoints are excluded from this spec. version: '2.0' contact: {} servers: - url: https://api.sandbox.conduit.financial/v2 description: Sandbox - url: https://api.conduit.financial/v2 description: Production security: - api-key: [] tags: - name: Customers - name: Registered Addresses - name: Wallets - name: Wallet Signers - name: Signing Quorum - name: Virtual Accounts - name: Applications - name: Documents - name: Verifications - name: Signing Requests - name: Transactions - name: Payouts - name: Whitelist Recipients - name: Orders - name: RFIs - name: Webhook Endpoints - name: Webhook Deliveries - name: Webhook Event Types - name: Features - name: Customer Onboarding - name: Sandbox paths: /applications/{id}: get: tags: - Applications summary: Get an application by ID description: >- Retrieves the full details of a single application. Use this to check the current status of an onboarding or feature request submission. operationId: ApplicationsController_findById_v2 parameters: - name: id required: true in: path schema: type: string responses: '200': description: The requested application content: application/json: schema: oneOf: - $ref: '#/components/schemas/CustomerOnboardingApplicationDto' - $ref: '#/components/schemas/CustomerUpdateApplicationDto' - $ref: '#/components/schemas/VirtualAccountFeatureApplicationDto' - $ref: '#/components/schemas/CryptoWalletFeatureApplicationDto' discriminator: propertyName: type '400': description: >- **INVALID_OID_FORMAT**: A path or query parameter expected a valid object identifier but received a value that does not match the expected format. content: application/json: schema: $ref: '#/components/schemas/ValidationErrorDto' example: type: INVALID_OID_FORMAT title: Invalid Object ID Format status: 400 detail: >- A path or query parameter expected a valid object identifier but received a value that does not match the expected format. resolution: >- Verify that all IDs in the request URL and query parameters are correctly formatted. IDs are typically prefixed strings like 'cus_...', 'app_...', or 'doc_...'. docs: https://conduit-v2.mintlify.app/errors#invalid-oid-format instance: /v2/... correlationId: req_a1b2c3d4 timestamp: '2026-01-15T09:30:00.000Z' '401': description: >- **API_KEY_MISSING**: The request did not include an API key. All API requests must be authenticated. **API_KEY_INVALID**: The provided API key is not recognized or has been revoked. content: application/json: schema: $ref: '#/components/schemas/ProblemDetailDto' example: type: API_KEY_MISSING title: API Key Missing status: 401 detail: >- The request did not include an API key. All API requests must be authenticated. resolution: >- Include your API key in the 'x-api-key' header with every request. docs: https://conduit-v2.mintlify.app/errors#api-key-missing instance: /v2/... correlationId: req_a1b2c3d4 timestamp: '2026-01-15T09:30:00.000Z' '404': description: >- **APPLICATION_NOT_FOUND**: No application exists with the specified ID, or the application belongs to a different organization. content: application/json: schema: $ref: '#/components/schemas/ProblemDetailDto' example: type: APPLICATION_NOT_FOUND title: Application Not Found status: 404 detail: >- No application exists with the specified ID, or the application belongs to a different organization. resolution: >- Verify the application ID is correct. Use the list applications endpoint to find valid application IDs for your organization. docs: https://conduit-v2.mintlify.app/errors#application-not-found instance: /v2/... correlationId: req_a1b2c3d4 timestamp: '2026-01-15T09:30:00.000Z' '429': description: >- **RATE_LIMITED**: Too many requests. This error is returned by three independent checks: the per-organization bucket applied to every authenticated API request; the per-IP bucket applied to unauthenticated traffic before an API key is validated; and the per-IP bucket applied when repeated invalid API keys are submitted from the same address. Honor the Retry-After header (also exposed as retryAfterSeconds in the body) before retrying. Current limits and remaining budget are visible in X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset on rate-limited route responses. content: application/json: schema: $ref: '#/components/schemas/RateLimitedErrorDto' example: type: RATE_LIMITED title: Rate Limited status: 429 detail: >- Too many requests. This error is returned by three independent checks: the per-organization bucket applied to every authenticated API request; the per-IP bucket applied to unauthenticated traffic before an API key is validated; and the per-IP bucket applied when repeated invalid API keys are submitted from the same address. Honor the Retry-After header (also exposed as retryAfterSeconds in the body) before retrying. Current limits and remaining budget are visible in X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset on rate-limited route responses. resolution: >- Sleep until Retry-After seconds have elapsed, then retry. For sustained workloads exceeding the per-organization defaults, request a rate-limit increase through your support contact. docs: https://conduit-v2.mintlify.app/errors#rate-limited instance: /v2/... correlationId: req_a1b2c3d4 timestamp: '2026-01-15T09:30:00.000Z' retryAfterSeconds: 3 '500': description: >- **INTERNAL_ERROR**: An unexpected error occurred while processing your request. content: application/json: schema: $ref: '#/components/schemas/ProblemDetailDto' example: type: INTERNAL_ERROR title: Internal Error status: 500 detail: An unexpected error occurred while processing your request. resolution: >- Retry the request after a brief delay. If the error persists, contact support and include the correlationId from the error response for investigation. docs: https://conduit-v2.mintlify.app/errors#internal-error instance: /v2/... correlationId: req_a1b2c3d4 timestamp: '2026-01-15T09:30:00.000Z' components: schemas: CustomerOnboardingApplicationDto: type: object properties: id: type: string pattern: ^app_[0-9A-Za-z]{22}$ description: Unique application identifier status: type: string enum: - pending - processing - approved - rejected - cancelled description: Current lifecycle status of the application example: pending clientReferenceId: description: >- Client-provided identifier for cross-referencing. Omitted when the client did not supply one. 1-255 characters from A-Za-z, 0-9, underscore, hyphen, colon, and period — no spaces. example: ext-12345 type: string pattern: ^[A-Za-z0-9_\-:.]{1,255}$ submittedAt: description: >- Timestamp when the application was submitted for review. Omitted while still in progress. type: string format: date-time example: '2026-01-15T09:30:00.000Z' createdAt: type: string format: date-time description: Timestamp when the application was created example: '2026-01-15T09:30:00.000Z' updatedAt: type: string format: date-time description: Timestamp when the application was last modified example: '2026-01-15T09:30:00.000Z' failureCode: description: >- Machine-readable failure code on rejected applications. Omitted on non-rejected applications. type: string enum: - rejected_by_ops - compliance_denied failureMessage: description: >- Customer-facing failure message accompanying `failureCode`. Omitted on non-rejected applications. type: string type: type: string enum: - customer_onboarding customerId: description: >- Customer this onboarding application produced. Omitted while the application is still being reviewed; present after approval persists the customer row. type: string pattern: ^cus_[0-9A-Za-z]{22}$ persons: description: >- People declared on the submission (beneficial owners and controlling persons), in submit order. Omitted before the application carries a submission. type: array items: type: object properties: referenceId: type: string description: >- Server-assigned stable reference for this person. Use it to fetch the person's identity-verification link (POST /v2/applications/{applicationId}/persons/{referenceId}/idv-link) and to correlate `idv_link.created` webhook events. name: type: string description: Person's name as submitted. required: - referenceId - name required: - id - status - createdAt - updatedAt - type CustomerUpdateApplicationDto: type: object properties: id: type: string pattern: ^app_[0-9A-Za-z]{22}$ description: Unique application identifier status: type: string enum: - pending - processing - approved - rejected - cancelled description: Current lifecycle status of the application example: pending clientReferenceId: description: >- Client-provided identifier for cross-referencing. Omitted when the client did not supply one. 1-255 characters from A-Za-z, 0-9, underscore, hyphen, colon, and period — no spaces. example: ext-12345 type: string pattern: ^[A-Za-z0-9_\-:.]{1,255}$ submittedAt: description: >- Timestamp when the application was submitted for review. Omitted while still in progress. type: string format: date-time example: '2026-01-15T09:30:00.000Z' createdAt: type: string format: date-time description: Timestamp when the application was created example: '2026-01-15T09:30:00.000Z' updatedAt: type: string format: date-time description: Timestamp when the application was last modified example: '2026-01-15T09:30:00.000Z' failureCode: description: >- Machine-readable failure code on rejected applications. Omitted on non-rejected applications. type: string enum: - rejected_by_ops - compliance_denied failureMessage: description: >- Customer-facing failure message accompanying `failureCode`. Omitted on non-rejected applications. type: string type: type: string enum: - customer_update customerId: type: string pattern: ^cus_[0-9A-Za-z]{22}$ description: Customer this update application belongs to. required: - id - status - createdAt - updatedAt - type - customerId VirtualAccountFeatureApplicationDto: type: object properties: id: type: string pattern: ^app_[0-9A-Za-z]{22}$ description: Unique application identifier status: type: string enum: - pending - processing - approved - rejected - cancelled description: Current lifecycle status of the application example: pending clientReferenceId: description: >- Client-provided identifier for cross-referencing. Omitted when the client did not supply one. 1-255 characters from A-Za-z, 0-9, underscore, hyphen, colon, and period — no spaces. example: ext-12345 type: string pattern: ^[A-Za-z0-9_\-:.]{1,255}$ submittedAt: description: >- Timestamp when the application was submitted for review. Omitted while still in progress. type: string format: date-time example: '2026-01-15T09:30:00.000Z' createdAt: type: string format: date-time description: Timestamp when the application was created example: '2026-01-15T09:30:00.000Z' updatedAt: type: string format: date-time description: Timestamp when the application was last modified example: '2026-01-15T09:30:00.000Z' failureCode: description: >- Machine-readable failure code on rejected applications. Omitted on non-rejected applications. type: string enum: - rejected_by_ops - compliance_denied failureMessage: description: >- Customer-facing failure message accompanying `failureCode`. Omitted on non-rejected applications. type: string type: type: string enum: - virtual_account customerId: type: string pattern: ^cus_[0-9A-Za-z]{22}$ asset: type: object properties: code: type: string enum: - USD - EUR - GBP - CHF - JPY - CAD - AUD - NZD - SGD - HKD - CNY - KRW - INR - BRL - MXN - ARS - CLP - COP - PEN - ZAR - NGN - KES - GHS - EGP - AED - SAR - ILS - TRY - PLN - CZK - HUF - SEK - NOK - DKK - THB - IDR - MYR - PHP - VND - TWD - USDC - USDT - DAI - EURC - PYUSD - BTC - ETH - SOL - TRX description: Asset code identifier example: USD chain: type: string enum: - ethereum - base - solana - polygon - arbitrum - optimism - avalanche - tron - stellar - bsc - bitcoin description: Blockchain network. `null`/omitted for fiat assets. nullable: true required: - code description: Target asset for this virtual-account feature application. required: - id - status - createdAt - updatedAt - type - customerId - asset CryptoWalletFeatureApplicationDto: type: object properties: id: type: string pattern: ^app_[0-9A-Za-z]{22}$ description: Unique application identifier status: type: string enum: - pending - processing - approved - rejected - cancelled description: Current lifecycle status of the application example: pending clientReferenceId: description: >- Client-provided identifier for cross-referencing. Omitted when the client did not supply one. 1-255 characters from A-Za-z, 0-9, underscore, hyphen, colon, and period — no spaces. example: ext-12345 type: string pattern: ^[A-Za-z0-9_\-:.]{1,255}$ submittedAt: description: >- Timestamp when the application was submitted for review. Omitted while still in progress. type: string format: date-time example: '2026-01-15T09:30:00.000Z' createdAt: type: string format: date-time description: Timestamp when the application was created example: '2026-01-15T09:30:00.000Z' updatedAt: type: string format: date-time description: Timestamp when the application was last modified example: '2026-01-15T09:30:00.000Z' failureCode: description: >- Machine-readable failure code on rejected applications. Omitted on non-rejected applications. type: string enum: - rejected_by_ops - compliance_denied failureMessage: description: >- Customer-facing failure message accompanying `failureCode`. Omitted on non-rejected applications. type: string type: type: string enum: - crypto_wallet customerId: type: string pattern: ^cus_[0-9A-Za-z]{22}$ required: - id - status - createdAt - updatedAt - type - customerId ValidationErrorDto: type: object properties: type: type: string description: Machine-readable error code example: CUSTOMER_NOT_FOUND title: type: string description: Human-readable error type label example: Customer Not Found status: type: number description: HTTP status code example: 404 detail: type: string description: Human-readable explanation of this occurrence example: Customer with id cus_abc123 not found resolution: type: string description: What the developer should do to resolve this error example: >- Verify the customer ID. Check you are using the correct API key for this organization. docs: type: string description: URL to error documentation example: https://conduit-v2.mintlify.app/errors#customer-not-found instance: type: string description: Request path that produced the error example: /v2/customers/cus_abc123 correlationId: description: Request correlation ID example: req_a1b2c3d4 type: string timestamp: type: string description: ISO 8601 UTC timestamp example: '2026-04-27T20:00:00.000Z' details: description: >- Additional structured data for domain-specific errors (e.g. missing field lists, pair info) errors: type: array items: type: object properties: pointer: type: string description: JSON pointer to the invalid field example: /email detail: type: string description: What is wrong with this field example: Invalid email format allowedValues: description: The values this field accepts, when it is a closed set example: - ach - fedwire - rtp type: array items: type: string category: description: >- Class of blocker (requirements-validator output only). 'field' = form-field gap, 'document' = missing or insufficient document (including per-UBO document slots), 'individual' = required person missing. example: field type: string enum: - field - document - individual required: - pointer - detail required: - type - title - status - detail - resolution - docs - instance - timestamp ProblemDetailDto: type: object properties: type: type: string description: Machine-readable error code example: CUSTOMER_NOT_FOUND title: type: string description: Human-readable error type label example: Customer Not Found status: type: number description: HTTP status code example: 404 detail: type: string description: Human-readable explanation of this occurrence example: Customer with id cus_abc123 not found resolution: type: string description: What the developer should do to resolve this error example: >- Verify the customer ID. Check you are using the correct API key for this organization. docs: type: string description: URL to error documentation example: https://conduit-v2.mintlify.app/errors#customer-not-found instance: type: string description: Request path that produced the error example: /v2/customers/cus_abc123 correlationId: description: Request correlation ID example: req_a1b2c3d4 type: string timestamp: type: string description: ISO 8601 UTC timestamp example: '2026-04-27T20:00:00.000Z' details: description: >- Additional structured data for domain-specific errors (e.g. missing field lists, pair info) required: - type - title - status - detail - resolution - docs - instance - timestamp RateLimitedErrorDto: type: object properties: type: type: string description: Machine-readable error code example: CUSTOMER_NOT_FOUND title: type: string description: Human-readable error type label example: Customer Not Found status: type: number description: HTTP status code example: 404 detail: type: string description: Human-readable explanation of this occurrence example: Customer with id cus_abc123 not found resolution: type: string description: What the developer should do to resolve this error example: >- Verify the customer ID. Check you are using the correct API key for this organization. docs: type: string description: URL to error documentation example: https://conduit-v2.mintlify.app/errors#customer-not-found instance: type: string description: Request path that produced the error example: /v2/customers/cus_abc123 correlationId: description: Request correlation ID example: req_a1b2c3d4 type: string timestamp: type: string description: ISO 8601 UTC timestamp example: '2026-04-27T20:00:00.000Z' details: description: >- Additional structured data for domain-specific errors (e.g. missing field lists, pair info) retryAfterSeconds: type: integer minimum: 0 exclusiveMinimum: true maximum: 9007199254740991 description: Seconds to wait before retrying example: 3 required: - type - title - status - detail - resolution - docs - instance - timestamp - retryAfterSeconds securitySchemes: api-key: type: apiKey in: header name: x-api-key ````