Endpoints
Fingerprint Lookup (Deprecated)
GET
Lookup the associated fingerprint to the Telemetry ID returned from the GetTelemetryID(). This endpoint is deprecated and clients should use the POST version of Fingerprint Lookup instead. Learn more about the different fingerprint types and verdicts in our DFP guide. Make a decision based on the returned verdict:Documentation Index
Fetch the complete documentation index at: https://stytch.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
ALLOW- This is a known valid device grouping or device profile that is part of the default ALLOW listed set of known devices by Stytch. This grouping is made up of verified device profiles that match the characteristics of known/authentic traffic origins.BLOCK- This is a known bad or malicious device profile that is undesirable and should be blocked from completing the privileged action in question.CHALLENGE- This is an unknown or potentially malicious device that should be put through increased friction such as 2FA or other forms of extended user verification before allowing the privileged action to proceed.
telemetry_id is not found, we will return a 404 telemetry_id_not_found error. We recommend treating 404 errors as a BLOCK, since it could be a sign of an attacker trying to bypass DFP protections by generating fake telemetry IDs.
Query parameters
The telemetry ID associated with the fingerprint getting looked up.
Response fields
Globally unique UUID that is returned with every API call. This value is important to log for debugging purposes; we may ask for this value to help identify a specific API call when helping you debug an issue.
The HTTP status code of the response. Stytch follows standard HTTP response status code patterns, e.g. 2XX values equate to success, 3XX values are redirects, 4XX are client errors, and 5XX are server errors.
A Stytch fingerprint consists of the following identifiers:
The metadata associated with each fingerprint