FOR DEVELOPERS
Browser Fingerprint API
Build checks around explainable browser signals. Existing endpoints expose the schema, create short-lived sessions, accept evidence and retrieve or compare reports.
The browser collects; the server builds reports
Canvas, WebGL and screen signals must be collected in an actual browser. An HTTP request alone cannot reveal a visitor’s complete fingerprint to the server. Standalone tools run locally; building a server report requires submitting collected results.
Current integration scope
These endpoints serve the site’s same-origin test workflow. They do not provide cross-origin browser access, API-key management, commercial quotas or an SLA. The documentation describes the current implementation, not a managed identity service.
Temporary data and explainable results
Sessions last 10 minutes and a nonce can be successfully used once. Reports live in process memory for up to 24 hours and may disappear earlier after a restart. Results describe the submitted observations without identifying users across visits.