HTTP Status Codes
Common Errors and Fixes
409 Conflict — 'Client ID already exists'
409 Conflict — 'Client ID already exists'
Cause: You’re generating a token for a
clientId that already has an active verification session.Fix:- Use a unique
clientIdper verification attempt - If your user needs to re-verify, either use a different
clientIdor wait for the previous session to expire
400 Bad Request — 'Invalid parameter'
400 Bad Request — 'Invalid parameter'
Cause: A required field is missing or a field value is invalid.Fix:
- Check the session parameters for required fields and valid values
- Ensure
clientIdis a non-empty string - Ensure country codes use ISO 3166-1 alpha-2 format
Webhook not received
Webhook not received
Possible causes:
- Webhook URL not configured — check Dashboard → Settings → Webhooks
- Your endpoint returned a non-2xx status — check server logs
- Firewall blocking iDenfy IPs — whitelist our IP ranges
- HTTPS certificate issue — ensure your cert is valid and not self-signed
- Webhook still processing — manual reviews can take several minutes
iFrame camera not working
iFrame camera not working
Cause: Browser security policies restrict camera access in third-party iFrames.Fix:
- Add
allow="camera; microphone"to the iFrame tag - Ensure your page is served over HTTPS
- Check that no
Permissions-Policyheader blocks camera access - Some browsers (Safari) have stricter iFrame policies — test across browsers