Request filtering
Block unwanted identification requests to prevent malicious actors from misusing your Fingerprint public API keys.
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.
- To filter requests from web browsers by origin or HTTP header, see Request filtering for websites.
- To filter requests from mobile applications by package names or bundle IDs, see Request filtering for mobile applications.
- To filter requests from common indexing and AI bots, see Search bot request filtering and AI bot request filtering respectively.
- To filter requests from a range of IP addresses, see Network request filtering.
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.
Updated 8 days ago