Skip to main content
Server API enables you to get more information about individual identification events (using the /events endpoint). Server API must 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). Server API requests are not billed and do not count towards your monthly allowance. The following Server APIs are available:
  • /v4/events/:event_id
    • GET a detailed payload for a single event defined by an event_id
    • PATCH an event with linked_id, tag and suspect flag
  • /v4/events
    • GET a list of event details using on a wide range of built-in filters (linked_id, visitor_id, start, end and suspect fields among others).

​
See Also

  • To identify the browsers that visit your web application, see our documentation for Javascript agent.
  • To identify the mobile devices that use your mobile app, see our documentation for Android and iOS.

​
Regions

The server API is available in the Global, EU and Asia (Mumbai) regions:
RegionBase URLServer Location
Globalhttps://api.fpjs.ioGlobal
EUhttps://eu.api.fpjs.ioFrankfurt, Germany
Asia (Mumbai)https://ap.api.fpjs.ioMumbai, India
Use the Base URL dropdown in the right column of each endpoint to select the correct base URL according to your workspace region.

​
Authentication

There is one standard way to authenticate against the API: Authorization: Bearer header. All unauthenticated requests will return HTTP 403 Forbidden response.

​
Authorization: Bearer HTTP header

When making an API request, add Authorization: Bearer <secret key> HTTP header with your secret API key. Example request including the API key in the Authorization header 
curl https://api.fpjs.io/v4/event/:event_id  \ 
     -H `Authorization: Bearer <secret key>`

​
Server API SDKs

​
Server SDKs for v4 API coming soon

We are working on new major versions of all our SDKs. If you need to use any of the following integrations, please use the v3 API instead or generate your own from the Server API OpenAPI schema.
For a smoother developer experience, we offer typed SDKs for these languages: Pick one of them as the Language on the endpoint page’s top right corner to see an example request using that SDK. The SDKs (and this reference) are based on a Server API OpenAPI schema, which is also available on Github:

​
Trying it out

You can try calling the Server API directly from this reference:
  1. You are going to need a Secret API Key. You can create one in your Fingerprint Dashboard > API Keys.
  2. To make a request, you will need either a visitorId or requestId of an identification event associated with your workspace. Go to Dashboard > Identification to see your identification events.
  3. Scroll down to one of the endpoints, for example, Get visits by visitorId.
  4. Set Authentication to your secret API key.
  5. Set the visitor_id path parameter to some visitor_id from your dashboard (or requestId in the case of Get event by requestId).
  6. Make sure the Base URL corresponds to your workspace region.
  7. Click Try it!
A real API response will appear in the Response section. Alternatively, you can view the prepared response examples there.