Use Related Visitors API to unify and personalize the experience for your anonymous users who visit your website from regular and in-app browsers.
Typically, the visitor ID generated for an in-app browser is different from that of a regular browser, even when these browsers belong to the same mobile device.
This API informs you that operations (1) and (2) in the image come from the same mobile device. You can then use that information to personalize your user’s experience across different platforms, strengthen your fraud detection engine, understand the performance of your A/B experiments, etc.
Using Related Visitors API
This API is intended to be used only from the server side; it was never designed to be and must not be used from the client side (i.e. browsers, mobile devices).
This API is available for all of our plans. If you are interested in using this API, please contact our support team to enable it for you. Otherwise, you will receive an error.
Pricing
This API is priced at $1 per 1000 API calls.
Authentication
Requests to Related Visitors API are authenticated using the Secret API key. When making a request, the HTTP Header Auth-API-Key must be set to the value of the Secret API Key.
If you don’t have a Secret API Key, you can create one on your Fingerprint Dashboard by visiting App Settings > API Keys.
It is also possible to authenticate the request by setting the query parameter api_key to the value of the Secret API Key. However, we strongly advise against it and recommend this approach only for quick tests.
https://api.fpjs.io/related-visitors/someVisitorId?api_key=your-secret-api-keyAvailability
This API is available in the Global, EU, and Asia regions:
| Region | Base URL | Server Location |
|---|---|---|
| Global | https://api.fpjs.io | Northern Virginia, USA |
| EU | https://eu.api.fpjs.io | Frankfurt, Germany |
| Asia | https://ap.api.fpjs.io | Mumbai, India |