Import customers from Persona Connect share tokens
Starts an asynchronous import job for Persona Connect share tokens (cnst_...).
For each token, Dakota redeems it with Persona, maps the verified identity data
into a new customer and individual application, and imports documents.
Unlike the Sumsub import, Persona redemption is asynchronous on Persona’s side,
so this endpoint returns immediately with a job. Poll
GET /customers/persona-import-jobs/{job_id} for per-token results. Tokens are
validated and de-duplicated up front; skipped tokens never block accepted ones.
A skipped token is a token string that could not be queued (malformed, a
duplicate in the batch, or already imported) — it is NOT a compliance decision
about a person or application.
Authorizations
Headers
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.
Body
Persona Connect share tokens (cnst_...) to import. Up to 5,000 per request — split larger migrations into multiple batches (each returns its own job).
1 - 5000 elementsResponse
Import job accepted and queued
Number of tokens accepted into the job
Number of token strings that could not be queued
Token strings that could not be queued, with their index and reason (malformed, duplicate in batch, or already imported). This is about the token string only — never a compliance decision about a person or application.

