Which credentials should my integration use?
Separate server keys, signed-in user sessions and SDK session capabilities.
Hosted server API
Use https://facexverify.com/api/v1 with a FaceX server key in the Authorization bearer header. Create and manage that key in Developer settings. Keep it in your server’s secret configuration, outside browser and mobile bundles.
Dashboard and wallet services
Console operations and wallet checkout use the signed-in user’s access token, with operation-specific permissions. A public publishable key does not replace a user session. Follow the authentication section of the API reference.
Workspace launch tokens
Your authenticated server creates a launch with POST https://facexverify.com/api/verification/launch or POST https://facexverify.com/api/v1/verifications. Pass the returned short-lived launchToken to the SDK. Keep your server key on your backend.
Contact support or email support@facexverify.com.