API parity

Each dashboard action has a matching API endpoint. Once you know which cases come up most for your customers, you can automate the same workflow.

In the panel	Endpoint
See what is outstanding	`GET /api/customers/{id}/requirements`
Status, step status, reject comment, EDD flag	`GET /api/identifications/{id}`
Mint a verification link to share	`POST /api/customers/{id}/identifications/v2` with `{ "type": "Link" }`. The response carries the `url` to send.
Start EDD	The same call with `"with_edd": true`
Read the submitted questionnaire	`GET /api/identifications/{id}/compliance-questionnaire`
Create new KYC	`POST /api/customers/{id}/identifications/v2`
Archive an identification	`POST /api/identifications/{id}/archive`
Terms signing state	`GET /api/customers/{id}/required-signings` and `GET /api/customers/{id}/signings`

Two panel actions have no public endpoint today: Upload documents, and the combined onboarding link that covers verification and terms signing in one URL. Programmatically, mint a verification link with identifications/v2 and drive signings through the signings endpoints. Everything else in the table is a direct equivalent.

See Onboarding for the full API flow, and Webhooks to get told when a customer’s status changes instead of watching this page.

Getting Started

Dashboard

Customer operations

Onboarding & Compliance

Addresses & Travel Rule

Autoramp & Transactions

Webhooks & Events

Billing & Settlement

Tutorials

Issuance

Wallets

Coverage

Support