Skip to main content
POST
Submit an attestation for an application

Authorizations

X-Application-Token
string
header
required

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 30 days and rate-limited to 250 requests per hour.

Headers

x-idempotency-key
string<uuid>
required

Unique key to ensure request idempotency. If the same key is used within a certain time window, the original response will be returned instead of executing the request again.

Path Parameters

application_id
string
required

The unique identifier for the application 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.

Required string length: 27
Pattern: ^[0-9A-Za-z]{27}$
Example:

"1NFHrqBHb3cTfLVkFSGmHZqdDPi"

Body

application/json

Attestation submission data

Request to submit an attestation for a KYB application.

To accept a banking partner's disclosure online (the customer-facing half of the partner-onboarding disclosure gate), additionally supply disclosure_id (the terms key the provider declared, e.g. partner_disclosures) and disclosure_version. When those fields are present the attestation is recorded as a partner disclosure acknowledgment with acceptance_channel = customer_online (acceptor name + client IP captured server-side), advancing the partner-onboarding substatus and — for an already-approved application — triggering the programmatic reprovision. The API is partner-agnostic: callers supply a terms key + version, never a partner name. When disclosure_id is absent the behavior is a standard onboarding attestation.

attestation_type
enum<string>
required

Type of attestation being submitted

Available options:
information_accuracy,
terms_of_service,
privacy_policy,
funds_transfer_agreement,
lead_bank_privacy_policy,
e_sign
Example:

"information_accuracy"

timestamp
integer<int64>
required

Unix epoch timestamp (in seconds) when the attestation was made

Example:

1705315800

applicant_id
string<ksuid>
required

ID of the individual applicant making the attestation

Example:

"2hCjxJzUAW6JVRkZqaF9E0KpM3b"

disclosure_id
string

Optional. The partner disclosure terms key the customer is accepting, as declared by the provider (e.g. partner_disclosures). When present, this attestation is recorded as a partner disclosure acknowledgment. Partner-agnostic — a terms key, never a partner name.

Example:

"partner_disclosures"

disclosure_version
string

Optional. The version of the partner disclosure being accepted (e.g. 2026-06). Required when disclosure_id is present.

Example:

"2026-06"

Response

Attestation submitted successfully