Skip to main content
To provide device intelligence, Fingerprint runs on the client device — inside the browser or a mobile application. Client-side code can be easily examined, therefore, the API key you use to make identification requests to Fingerprint is by definition a public API key. To prevent malicious actors from misusing your public API key and inflating your Fingerprint costs, you can filter out unwanted identification requests. These requests are not billed and will receive an error instead of the identification result.
We rolled out the beta for Request Filtering V2.New iteration of request filtering gives you more flexibility and control when blocking unwanted identification requests. You have full control over order of execution, and you can create more complex rules by using our flexible expression language.
What’s Next