Fingerprint Pro Server API

Name: Fingerprint Pro Server API API
Brand: Fingerprint Pro Server API
Availability: InStock

✓ Official Vendor SpecSecurityThreat DetectionapiKey, bearer3 EndpointsREST

For Agents

Verify a visitor's identification, fraud signals, and history via three regional endpoints using a secret API key in the Auth-API-Key header.

Connect the Fingerprint Pro Server API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Fingerprint Pro Server API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Fingerprint Pro Server API API.

Look up an identification event by request_id to confirm the device and surface smart signals

Pull a visitor's full history from GET /visitors/{visitor_id} to spot multi-account abuse

Honour data-deletion requests by calling DELETE /visitors/{visitor_id}

Read bot, VPN, and tampering signals before approving a high-risk transaction

GET STARTED

Start building with Fingerprint Pro Server API API

Explore with Jentic

View OpenAPI Document

The Fingerprint Pro Server API gives backends programmatic access to browser and device fingerprinting data captured by Fingerprint Pro, including identification events, smart signals (bot detection, VPN detection, tampering detection), and per-visitor history. It exposes three endpoints across three regional hosts (US, EU, and Asia-Pacific). Authentication is by a secret API key sent either in the Auth-API-Key header or as a Bearer token. The API is used by fraud, account security, and abuse teams that need to verify whether a request comes from a returning real visitor or a bot before allowing high-risk actions.

Use Cases

Patterns agents use Fingerprint Pro Server API API for, with concrete tasks.

★ High-Risk Transaction Verification

Payments and account teams can have an agent receive the requestId from the client SDK at checkout, call GET /v4/events/{request_id}, and consult bot, VPN, and tampering signals before approving the order. If signals are clean and the visitor has prior trusted history via GET /visitors/{visitor_id}, the agent can fast-track; otherwise it can step up to an additional verification.

Receive requestId from the client, call GET /v4/events/{request_id}, then GET /visitors/{visitor_id}; approve when bot=false and history is clean, otherwise step up.

Multi-Account Abuse Detection

Trust and safety teams can have an agent walk new account signups, pull GET /visitors/{visitor_id} for each, and flag visitors with an unusual number of distinct user_ids in their history. Because Fingerprint provides a stable visitor id even across cleared cookies, the agent catches multi-account abuse that pure cookie checks miss.

On signup, call GET /visitors/{visitor_id}; if the visitor has more than three distinct linked accounts in the last 30 days, flag for review.

GDPR-Compliant Data Deletion

Compliance teams can wire user data-deletion requests to an agent that calls DELETE /visitors/{visitor_id} on Fingerprint, in addition to deleting host-application records. Fingerprint then removes that visitor's identification history server-side, helping the host meet GDPR right-to-erasure obligations without manual intervention.

On a data deletion request, look up the visitor id linked to the user and call DELETE /visitors/{visitor_id} on the appropriate regional host.

AI Agent Fingerprint Integration via Jentic

An agent connected to Jentic can search by intent (for example check whether this request is a bot) and Jentic returns the matching Fingerprint operation along with its input schema. The Auth-API-Key lives in the vault, so the agent never embeds the secret key. Integration drops from a multi-day Fingerprint setup to under an hour.

Search Jentic for check fingerprint smart signals, load GET /v4/events/{request_id}, and execute with the requestId while Jentic injects the API key from the vault.

Key Endpoints

3 endpoints — the fingerprint pro server api gives backends programmatic access to browser and device fingerprinting data captured by fingerprint pro, including identification events, smart signals (bot detection, vpn detection, tampering detection), and per-visitor history.

METHOD

PATH

DESCRIPTION

GET

/v4/events/{request_id}

Retrieve an identification event and its smart signals

GET

/visitors/{visitor_id}

Get a visitor's identification history

DELETE

/visitors/{visitor_id}

Delete a visitor's history (GDPR right to erasure)

GET

/v4/events/{request_id}

Retrieve an identification event and its smart signals

GET

/visitors/{visitor_id}

Get a visitor's identification history

DELETE

/visitors/{visitor_id}

Delete a visitor's history (GDPR right to erasure)

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Fingerprint Auth-API-Key (or Bearer) secret keys are stored encrypted in the Jentic vault. Agents receive scoped references; the raw key never enters the agent's context, which matters because the key can read every visitor in the workspace.

Intent-based discovery

Agents search Jentic by intent (for example check whether a request is a bot) and Jentic returns the Fingerprint event lookup operation with its input schema, so the agent calls the right endpoint without reading the spec.

Time to first call

Direct Fingerprint integration: 1-2 days for client SDK, server-side verification, and regional routing. Through Jentic: under one hour to wire the server-side calls (the client SDK still installs separately).

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Auth0 Management API

Identity and login that pairs with Fingerprint smart signals for step-up auth

Use Auth0 alongside Fingerprint when smart signals should trigger step-up authentication via Auth0 actions.

Complementary

Okta API

Workforce and customer identity to combine with Fingerprint device signals

Use Okta alongside Fingerprint when an enterprise needs identity governance combined with device fingerprinting.

Alternative

IP Geolocation API

Lighter-weight IP-only signal rather than full device fingerprinting

Choose IP Geolocation when only coarse country and ASN signals are needed; pick Fingerprint when you need a stable per-device identifier.

FAQs

Specific to using Fingerprint Pro Server API API through Jentic.

What authentication does the Fingerprint Pro Server API use?

Fingerprint accepts a secret API key in the Auth-API-Key header or as a Bearer token in the Authorization header. Through Jentic the secret key lives in the encrypted vault and is injected at execution; the agent only ever sees a vault reference.

Can I check bot signals before approving a checkout?

Yes. Take the requestId returned by the Fingerprint client SDK and call GET /v4/events/{request_id} from your backend. The response includes the bot, VPN, and tampering smart signals you can use as the gating decision before approving the transaction.

What are the rate limits for the Fingerprint Pro Server API?

Fingerprint applies per-API-key rate limits that scale with your plan tier. The vendor recommends backing off on 429 responses with exponential delay and avoiding bursting on /visitors/{visitor_id} during sign-up surges.

How do I delete a visitor for a GDPR request via Jentic?

Search Jentic for delete a fingerprint visitor, load DELETE /visitors/{visitor_id}, and execute with the visitor id. Jentic injects the Auth-API-Key from the vault and Fingerprint removes the visitor's history.

Can I use a regional Fingerprint host for data residency?

Yes. The spec lists three regional bases - api.fpjs.io for the global/US region, eu.api.fpjs.io for EU, and ap.api.fpjs.io for Asia-Pacific - so you can route calls to the host that matches your data residency requirements.

Is the Fingerprint Pro Server API free to use?

Fingerprint offers a free trial with limited identification events; production use requires a paid Pro or Enterprise plan. The API endpoints are the same across plans, with quotas applied per API key.