canonical: https://jentic.com/apis/idenfy.com/idenfy

# iDenfy Identity Verification API

Jentic publishes the only available OpenAPI specification for iDenfy Identity Verification API, keeping it validated and agent-ready. iDenfy is a Lithuanian KYC and identity verification platform offering document verification, biometric face matching, and AML screening. The /token endpoint creates a verification session for a client, returning an authentication token that the front-end SDK uses to walk the user through document capture and selfie matching. Verification results are delivered via callback to the integrator and queryable through the dashboard.

## For AI agents

Create iDenfy verification sessions that drive document and biometric identity checks for KYC onboarding flows.

## Scope

Does not handle ongoing AML monitoring, sanctions watchlist updates, or transaction screening - use for one-off identity verification session creation only.

## Capabilities

- Create a verification session token tied to a specific client identifier via POST /token
- Configure session-level options for document type, locale, and callback URL at session creation
- Hand off the returned token to the iDenfy front-end SDK so the user completes document capture
- Trigger biometric selfie matching as part of the same session token
- Drive AML screening for the client identified by the verification session

## Use cases

### Regulated Account Onboarding

A regulated platform - neobank, broker, crypto exchange - onboards a new customer by creating an iDenfy verification session via POST /token. The customer completes document capture and a selfie in the iDenfy SDK, and the backend receives a verification verdict via callback. Most integrations are live within 1-2 days because the session-token model removes the need to host any document handling in the integrator's stack.

Example prompt: Call POST /token with the client ID and locale, then return the token to the front-end SDK and wait for the verification callback

### Marketplace Seller Verification

A marketplace requires sellers to complete identity verification before listing high-value items. The agent creates an iDenfy session for the seller through /token and gates listing creation behind a successful callback. This protects the marketplace from fraudulent sellers without requiring buyers to verify too.

Example prompt: Call POST /token with the seller's client ID and a callback URL pointing to the marketplace's listing-gating service

### Age and Document Type Restricted Sign-Up

When a service is restricted by age or document type - for example only government-issued IDs from specific countries - the integrator passes the constraint at session creation and iDenfy's flow enforces it. The verification verdict returned via callback indicates whether the constraint was satisfied.

Example prompt: Call POST /token with allowedDocumentTypes restricted to passport and the user's expected country, then act on the callback verdict

### AI Agent Compliance Onboarding

A compliance agent uses Jentic to find iDenfy operations matching 'verify a new customer for KYC', loads the /token schema, and creates a verification session for each new sign-up. The agent returns the SDK-ready token to the front-end and listens for the callback to advance the user's onboarding state.

Example prompt: Use Jentic search 'verify a new customer for KYC' to load the iDenfy /token schema and execute it with the new user's client ID

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/token` | Create a verification session token tied to a client identifier |

## Key resources

- **Identity Verification** — Session token creation that drives the document and biometric verification flow

## Why Jentic

- **Setup:** Wiring the iDenfy Identity Verification API by hand means passing your key in the Authorization header and shaping the verification session token request yourself. Through Jentic you install once, import the iDenfy Identity Verification API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** iDenfy takes the session details in the request body rather than a resource path, so limit the agent to the single operation it needs, creating a verification session token. Because you name that one allowed operation, the agent can start verification sessions and do nothing else.
- **Credential handling:** Your iDenfy API 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.
- **Discovery method:** Agents search Jentic by intent such as 'start an identity verification session', and Jentic returns the matching iDenfy operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Onfido API** — UK-based identity verification competitor with broader API surface for case management
- **Veriff API** — Estonian identity verification competitor with similar session-based document and biometric flow
- **Sumsub API** — Identity verification and AML platform with extensive applicant and case-management endpoints

## FAQ

### Why is there no official OpenAPI spec for iDenfy Identity Verification API?

iDenfy does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call iDenfy Identity Verification API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the iDenfy Identity Verification API use?

The iDenfy API uses an API key passed in the Authorization header. Keys are issued from the iDenfy dashboard and are tied to a merchant account. Through Jentic, the key is stored encrypted in your Jentic One instance and injected at execution time, so it never enters the agent's prompt context.

### Can the iDenfy API perform biometric face matching?

Yes. The verification session created via POST /token can include a selfie step that matches the user's live face against the photo on the verified document. The matching result is delivered to the integrator via the configured callback URL after the user completes the SDK flow.

### What are the rate limits for the iDenfy Identity Verification API?

iDenfy applies per-account rate limits and a monthly verification quota tied to the merchant agreement. The OpenAPI spec does not encode hard thresholds. Design agents to handle 429 responses with backoff and to create one session token per user rather than reusing tokens across users.

### How do I create a verification session through Jentic?

Run pip install jentic and import the SDK, then await client.search('verify a new customer for KYC') to find the iDenfy /token operation. Load the schema and execute with the client ID and locale, then pass the returned token to the iDenfy front-end SDK. Run Jentic One, the self-hosted execution layer, for an API key.

### Where is the verification result delivered?

Verification verdicts are not returned synchronously from /token - instead they are delivered to the callback URL configured at session creation, and are also visible in the iDenfy dashboard. Build the agent to listen for the callback and advance the user's onboarding state when it arrives.

### Can I limit what my agent is allowed to do with the iDenfy Identity Verification API?

Yes. Because you run Jentic One yourself, your own rules decide which iDenfy operations and credentials the agent may use, and the iDenfy API exposes just one operation: creating a verification session token via POST /token. Since iDenfy takes the session details in the request body rather than a resource path, you scope the agent by naming that single allowed operation, so it can start verification sessions and nothing else. Your iDenfy API key is held encrypted by your own instance and injected only at execution time, so the agent never sees the raw credential.