What does this integration error mean?

Short answer

Use the HTTP status and stable error code to identify the problem. Check the correct product, key type and environment before retrying. An authentication failure, a rejected input and a customer verification decline are different situations.

Start with the common causes

• 401: check that the complete active key was sent in the expected Bearer header. A revoked key cannot be reused.
• Secret key required: move the sensitive read to your backend and use the correct secret key. Do not put that key into a browser to bypass the error.
• Environment mismatch or missing resource: confirm that the key, host, workflow and resource all belong to the same environment.
• Workflow unavailable: check publication, organisation and environment. A draft cannot act as a published flow.
• Validation error: read the structured response for the field that needs correction. Retry the corrected input rather than repeatedly sending the same invalid request.
• Rate limited: apply the documented backoff and limits. Repeated immediate retries can prolong the problem.

Separate pending work from failure

An in-progress verification means the applicant has not yet submitted. Processing can mean checks are running or the workflow is waiting for evidence. An SDK on-submit callback does not mean the decision is available. Prefer the documented notifications and status response to aggressive polling.

A system or provider error is not evidence that the applicant failed identity checks. Use the error guidance and current status before asking for another attempt.

If you need help

Check the service status page, then contact Toden with the request time, environment, endpoint, HTTP status, error code and request reference where available. Redact personal data. Never send an API key, signing secret or applicant link in a general support message.

Related guides

• Troubleshooting by error
• Error reference