Skip to main content
Submit a verification request after obtaining the data subject’s lawful authorisation and confirming the exact consent text. Include an Idempotency-Key header on every submission. Store the returned sessionId and poll it, or wait for a signed webhook.

Authentication

string
required
Your workspace API key.
string
required
Your workspace API secret.
string
required
Must be application/json.
string
required
Unique request identifier, 8-100 characters: letters, digits, or ._:-. Retry with the same key and identical body to avoid duplicates. See Idempotency.

Request body

string
required
Product code from GET /catalog. Examples: nin, tin, business, phone.
object
required
Identity fields required by the chosen product. Use exact selection values and date fields in YYYY-MM-DD format. See the Products reference for per-product field lists.
Must be true. Confirms that the data subject has been presented with the exact consent text and has genuinely confirmed.
The exact consent text returned by POST /verifications/consent for the same product and fields.

Response fields

string
required
API request ID.
object

Status codes

Do not create another check while a session is pending. Poll the saved session no more frequently than every 15 seconds.
A 202 response means the verification is still processing. Store the sessionId and poll GET /verifications/:sessionId at most every 15 seconds, or rely on verification.completed webhooks.