Skip to content
FaceX Verify
API & SDK INTEGRATION

How do I troubleshoot API errors?

Check credentials, mode, service readiness and the returned error.

FXFaceX SupportUpdated · 1 min read

Check the request

Verify the base URL, route, method and authorization used for that service. For the hosted gateway, 401 can indicate an invalid, revoked or environment-mismatched key; 403 can indicate missing Live compliance approval.

Check service readiness

A 202 launch response starts capture; it is not an approval. A 503 response can indicate missing processor configuration or an unavailable workspace database. NIN is unsupported and returns 422. For 429, back off before another request and check the current gateway limits.

Share a redacted report

Include the route, HTTP status, error code, timestamp with timezone, selected mode and request ID if one was returned. Remove secrets, identifiers, document bytes and biometric data. See the error reference for exact deployed behavior.

Contact support or email support@facexverify.com.

Which credentials should my integration use?Separate server keys, signed-in user sessions and SDK session capabilities.What is included in the FaceX SDKs?Understand Web, Android and iOS client scope before integrating.How should I handle timeouts and cancellation?Recover without duplicating attempts or leaving a session active.