Test your integration
Each Stytch project has a single live environment and multiple test environments, each with its own public token. Use the live token only in production. Use test tokens in development and pre-production—they’re isolated from billing, so you won’t be charged.
Scenarios and telemetry IDs for testing
You should test the following scenarios for your Fingerprint Lookup API calls:
- ALLOW verdict action
- BLOCK verdict action
- CHALLENGE verdict action
- telemetry_id is null, not provided, or some other value that was not created using GetTelemetryID()
- This will result in a 404 error from /lookup
- The /lookup API responds with...
Please log in to access this page.
For security, this page is restricted to workspaces using Stytch Device Fingerprinting.
Log in to StytchInterested in device fingerprinting?
Add fraud protection to your auth stack with advanced device fingerprinting that goes beyond CAPTCHA and WAF.
Get started