Kantos

The KYC Verification API mints a fresh identity-verification link for a lead using your Didit integration. Use it when a verification link has expired or a customer needs a new one — the lead's existing verification record is updated in place, so no duplicate records are created.

Requires the Didit integration

This endpoint is available once the Identity Verification (KYC) integration is installed and enabled for your organization. Verification links are issued by Didit and expire according to the workflow you configure in the Didit console.

Regenerate a Verification Link

Create a new verification session for a lead and refresh both the lead's kyc_verification_url and its linked KYC verification record:

curl -X POST "https://kantos.ai/api/crm/kyc/regenerate" \
  -H "X-Api-Key: kantos_your_secret_key" \
  -H "Content-Type: application/json" \
  -d '{ "lead_id": "b1e0c2a4-1234-5678-9abc-def012345678" }'

Request Body

Field	Type	Description
`lead_id`	string (UUID)	Required. The lead record to (re)issue a verification link for.

Response

{
  "success": true,
  "verification_url": "https://verification.didit.me/session/..."
}

Send the verification_url to your customer — or let your reminder emails and customer dashboard pick it up automatically, since both read the refreshed value from the lead.

Errors

Status	When
`400`	Missing or non-UUID `lead_id`, the Didit integration is disabled, or a verification is already in progress for this lead.
`401`	Missing or invalid API key.
`404`	The lead does not exist in your organization.
`429`	Rate limit exceeded.

Refreshing many links at once

To clear a batch of expired links, loop this endpoint over your lead IDs. Each lead keeps a single KYC verification record that is updated with the newest session, so re-running is safe and never pollutes the CRM with duplicates.

Next Steps

Records API — Find the lead IDs to pass in
Native Integrations — Set up Didit KYC verification
Rate Limits — Understand request quotas