Jumio API

Name: Jumio API
Brand: Jumio API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIdentity AuthIdentity Verificationbearer10 EndpointsREST

For Agents

Run identity verification workflows on Jumio: create accounts, kick off verification executions, and retrieve the verified document data, biometric results, and transaction images.

Install Jentic One Beta

Connect the Jumio API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Jumio 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.

Step 1: 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

Step 2: 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 Jumio API.

Create and manage Jumio verification accounts via /accounts and update account profile data

Initiate identity proofing workflow executions and poll their status until verification completes

Issue and rotate API credentials scoped to a specific account through /accounts/{accountId}/credentials

GET STARTED

Start building with Jumio API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Jumio API, keeping it validated and agent-ready. The Jumio API powers KYC, AML, and identity verification flows by orchestrating workflow executions against verification accounts. It supports document capture, biometric checks, and credential lifecycle management, exposing endpoints to create accounts, run workflow executions, and retrieve transaction results and images. Integrations span web and mobile SDKs, with the REST surface used to create credentials, query verification status, and pull final transaction data for downstream review.

Use Cases

Patterns agents use Jumio API for, with concrete tasks.

★ Onboarding KYC for Fintech Signups

When a new user signs up to a regulated fintech, the application creates a Jumio account, initiates a workflow execution, and waits for the user to capture their ID and selfie. Once the workflow finishes, the backend retrieves the transaction reference data to gate account funding on a passing decision. Most onboarding flows complete in under five minutes including capture and review.

Create a Jumio account for user 'jane@example.com', start a workflow execution, poll status until finished, then call /retrieval/{transactionReference} and return the verification decision.

Document Image Audit Trail

Compliance teams need to retrieve and archive the original document and selfie images captured during verification. The Jumio API exposes /retrieval/{transactionReference}/images/{imageId} so a server-side job can pull each image for a given transaction and store it in the firm's regulated record system. This replaces manual screenshot collection and keeps audit data tied to the verification reference.

For transaction reference 'tx-789', list available image IDs and download each via /retrieval/tx-789/images/{imageId} into S3 bucket 'kyc-archive'.

Workflow Status Reconciliation

Long-lived verification workflows can stall when users abandon capture or fail liveness. A reconciliation job lists workflow executions for an account using GET /accounts/{accountId}/workflow-executions and inspects per-execution detail, then nudges or expires stuck verifications. This prevents incomplete verifications from blocking account activation.

List all workflow executions for accountId 'acct-42' from the last 24 hours, identify any with status 'PENDING' older than 12 hours, and surface them for manual review.

Agent-Driven Customer Verification

An AI support agent handling a high-risk transaction escalation can trigger a fresh Jumio re-verification through Jentic. The agent searches for 'start an identity verification', loads the workflow execution schema, creates an account if needed, and returns the user-facing capture URL. This puts an enterprise-grade KYC step directly inside an agent flow without exposing raw API keys.

Through Jentic, search 'start an identity verification', load the Jumio workflow-executions operation, execute it for accountId 'acct-99', and return the redirect URL to the customer.

Key Endpoints

10 endpoints — jentic publishes the only available openapi specification for jumio api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/accounts

Create a new verification account

POST

/accounts/{accountId}/workflow-executions

Initiate a verification workflow execution

GET

/accounts/{accountId}/workflow-executions/{workflowExecutionId}

Get workflow execution details and decision

GET

/accounts/{accountId}/status

Get account verification status

GET

/retrieval/{transactionReference}

Retrieve transaction data for a completed verification

GET

/retrieval/{transactionReference}/images/{imageId}

Retrieve a captured document or selfie image

POST

/accounts

Create a new verification account

POST

/accounts/{accountId}/workflow-executions

Initiate a verification workflow execution

GET

/accounts/{accountId}/workflow-executions/{workflowExecutionId}

Get workflow execution details and decision

GET

/accounts/{accountId}/status

Get account verification status

GET

/retrieval/{transactionReference}

Retrieve transaction data for a completed verification

Why Jentic?

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

Credential isolation

Jumio bearer tokens are stored in the Jentic vault. Agents receive scoped session access and never see the raw token, so KYC credentials cannot leak into prompts or logs.

Intent-based discovery

Agents search Jentic by intent (e.g. 'start an identity verification') and Jentic returns the matching Jumio operation with its input schema, so the agent can call /accounts/{accountId}/workflow-executions without browsing Jumio's documentation.

Time to first call

Direct Jumio integration: 1-2 weeks for account provisioning, callback wiring, and webhook handling. Through Jentic: under 1 hour to search, load schema, and execute the first verification.

FAQs

Specific to using Jumio API through Jentic.

Why is there no official OpenAPI spec for Jumio API?

Jumio does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Jumio API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Jumio API use?

The Jumio API uses bearer token authentication via the Authorization header. Tokens are issued per account using POST /accounts/{accountId}/credentials. Through Jentic the bearer token is held in the encrypted vault and never enters the agent context.

Can I retrieve the captured document images for a verification?

Yes. After a workflow execution completes, GET /retrieval/{transactionReference} returns the verification result and image references, and GET /retrieval/{transactionReference}/images/{imageId} returns the binary image for archiving.

What are the rate limits for the Jumio API?

Jumio enforces per-account rate limits that scale with your contract tier; the spec does not pin a fixed value. Production integrations typically batch retrievals and use exponential backoff on 429 responses.

How do I start a KYC verification with the Jumio API through Jentic?

Search Jentic for 'start an identity verification', load the POST /accounts/{accountId}/workflow-executions operation schema, then execute with the user's accountId. Jentic returns the workflow ID you can poll until complete.

How do I check whether a user has passed verification?

Call GET /accounts/{accountId}/status for the current account-level decision, or GET /accounts/{accountId}/workflow-executions/{workflowExecutionId} for per-execution detail including the final decision and reason codes.

Jumio API

Connect the Jumio API to your agent

Capabilities

Start building with Jumio API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs