Veriff Public API

Name: Veriff Public API API
Brand: Veriff Public API
Availability: InStock

✓ Official Vendor SpecIdentity AuthIdentity VerificationapiKey13 EndpointsREST

For Agents

Programmatically create a verification session, update a verification session. Covers 13 operations with apiKey authentication.

Quickstart

Get started with Veriff Public API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a verification session"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Veriff Public API API.

Create a verification session

Update a verification session

Delete a verification session

Upload media for a session

Query session media

GET STARTED

Start building with Veriff Public API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Veriff Public API API for, with concrete tasks.

★ Identity and Authentication Operations

Use the Veriff Public API to perform identity auth operations programmatically. The API provides 13 endpoints covering core functionality including create a verification session, update a verification session, delete a verification session.

Call POST /sessions to create a verification session

Automated Sessions Management

Automate sessions operations by combining multiple Veriff Public API endpoints. Agents can update a verification session and then delete a verification session in a single workflow.

Call PATCH /sessions/{sessionId} to update a verification session, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Veriff Public API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Search Jentic for 'create a verification session', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

13 endpoints — veriff's identity verification api allows you to create verification sessions, upload end-user media, and retrieve verification decisions.

METHOD

PATH

DESCRIPTION

POST

/sessions

Create a verification session

PATCH

/sessions/{sessionId}

Update a verification session

DELETE

/sessions/{sessionId}

Delete a verification session

POST

/sessions/validate-registry

Create session and validate national ID

POST

/sessions/{sessionId}/media

Upload media for a session

GET

/sessions/{sessionId}/media

Query session media

POST

/sessions/{sessionId}/collected-data

Upload collected data

GET

/sessions/{sessionId}/decision

Get verification decision

POST

/sessions

Create a verification session

PATCH

/sessions/{sessionId}

Update a verification session

DELETE

/sessions/{sessionId}

Delete a verification session

POST

/sessions/validate-registry

Create session and validate national ID

POST

/sessions/{sessionId}/media

Upload media for a session

Why though Jentic?

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

Credential isolation

Veriff Public API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'create a verification session') and Jentic returns the matching Veriff Public API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Veriff Public API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Auth0

Alternative identity auth API

Choose Auth0 when you need a different approach to identity auth operations

Alternative

Okta

Alternative identity auth API

Choose Okta when you need a different approach to identity auth operations

FAQs

Specific to using Veriff Public API API through Jentic.

What authentication does the Veriff Public API use?

The Veriff Public API uses an API key passed in the `x-auth-client` header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I create a verification session with the Veriff Public API?

Yes. Use the POST /sessions endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Veriff Public API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I create a verification session through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'create a verification session'. Jentic returns the matching Veriff Public API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Veriff Public API have?

The Veriff Public API exposes 13 endpoints covering sessions, media, decisions operations.