Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Security / Fingerprint Pro Server API
Fingerprint Pro Server API logo

Fingerprint Pro Server API

68
AI ReadinessAI-Aware (B+)68/100
See full scorecard
Official vendor OpenAPI document · agent-readySecurityThreat 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.

Use for: Look up a Fingerprint identification event by request id, Get the visitor history for a given visitor id, Delete a Fingerprint visitor record on user request, Check whether a request was flagged as a bot

Not supported: Does not handle login, session management, or KYC document verification - use for visitor identification, smart fraud signals, and visitor history only.

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.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

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.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffingerprint.com%2Ffingerprint" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ffingerprint.com%2Ffingerprint" | 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.

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

Switch between US, EU, and Asia-Pacific hosts to satisfy data-residency requirements

Use Cases

Patterns agents use Fingerprint Pro Server 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)

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

F

Fingerprint Pro Server API

- AI-Aware (B+)
68/100
100
Foundational Compliance
61
Developer Experience & Jentic Compatibility
49
AI-Readiness & Agent Experience
94
Agent Usability
55
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4
99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

61

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

93%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

49

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D+Signals: 4
35%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

60%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

55

Security

Trust, risk posture, and security compliance.

Grade: CSignals: 1
55%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Fingerprint Pro Server API by hand means handling its Auth-API-Key header or bearer scheme, picking the right regional host among api.fpjs.io, eu.api.fpjs.io, and ap.api.fpjs.io, and managing retries yourself. Through Jentic you install once, import Fingerprint from the API Directory, store the key once, and your agent calls it.

Permission scoping

Fingerprint puts the visitor id in the URL path (/visitors/{visitor_id}), so a rule can pin your agent to one visitor: it can read that visitor's history and nothing else. You choose the operations it may call, so the destructive visitor deletion is not included unless you add it.

Credential isolation

Your Fingerprint key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'check whether a request is a bot' or 'look up a visitor's history', and Jentic returns the matching Fingerprint operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

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 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.

Can I limit what my agent is allowed to do with the Fingerprint Pro Server API?

Yes. Because you run Jentic One yourself, your own rules decide which Fingerprint operations and credentials the agent may use. You can allow it to read an identification event with GET /v4/events/{request_id} and a visitor's history with GET /visitors/{visitor_id} while withholding the destructive DELETE /visitors/{visitor_id} unless you explicitly add it. Since the visitor id sits in the URL path, a rule can even pin the agent to a single visitor so it reads that visitor's history and nothing else.

GET STARTED

Start building with Fingerprint Pro Server API

Explore with Jentic One
View OpenAPI Document