Sumsub API

Name: Sumsub API
Brand: Sumsub API
Availability: InStock

✓ Official Vendor SpecPaymentsPayment ProcessingapiKey82 EndpointsREST

For Agents

Programmatically api health, change top-level information. Covers 82 operations with apiKey authentication.

Use for: I need to api health, I want to change top-level information, Search for change required documents, Find all required id documents

Install Jentic One Beta

Connect the Sumsub API to your agent

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

API health

Change top-level information

Get required ID documents

Add ID document

GET STARTED

Start building with Sumsub API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Sumsub API for, with concrete tasks.

★ Payments Operations

Use the Sumsub API to perform payments operations programmatically. The API provides 82 endpoints covering core functionality including api health, change top-level information, change required documents.

Call GET /resources/status/api to api health

Automated Applicant Management

Automate applicant operations by combining multiple Sumsub API endpoints. Agents can change top-level information and then change required documents in a single workflow.

Call PATCH /resources/applicants to change top-level information, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Sumsub 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 'api health', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

82 endpoints — sumsub is the one verification platform to secure the whole user journey.

METHOD

PATH

DESCRIPTION

GET

/resources/status/api

API health

PATCH

/resources/applicants

Change top-level information

POST

/resources/applicants/{applicantId}/moveToLevel

Change required documents

POST

/resources/applicants/{applicantId}/requiredIdDocs

Get required ID documents

POST

/resources/applicants/{applicantId}/info/idDoc

Add ID document

PATCH

/resources/applicants/{applicantId}/fixedInfo

Change provided information

PATCH

/resources/applicants/{applicantId}/info

Change extracted information

POST

/resources/applicants/-/ingestCompleted?levelName={levelName}

Import applicants

GET

/resources/status/api

API health

PATCH

/resources/applicants

Change top-level information

POST

/resources/applicants/{applicantId}/moveToLevel

Change required documents

POST

/resources/applicants/{applicantId}/requiredIdDocs

Get required ID documents

POST

/resources/applicants/{applicantId}/info/idDoc

Add ID document

Why Jentic?

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

Credential isolation

Sumsub 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., 'api health') and Jentic returns the matching Sumsub API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

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

FAQs

Specific to using Sumsub API through Jentic.

What authentication does the Sumsub API use?

The Sumsub API uses an API key passed in the `X-App-Token` 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 api health with the Sumsub API?

Yes. Use the GET /resources/status/api endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Sumsub 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 api health through Jentic?

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

How many endpoints does the Sumsub API have?

The Sumsub API exposes 82 endpoints covering applicant, transaction, check operations.

Sumsub API

Connect the Sumsub API to your agent

Capabilities

Start building with Sumsub API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs