Unit API launch
New feature Starting November 4, 2026, the Unit API lets you call identity verification capabilities one at a time. You can attach ID OCR, face comparison, government record verification, and more directly to your service without going through the Liveform submission flow.- One call returns one result. No submission is created.
- Every call is synchronous. You receive the result in the response, and there are no webhooks.
- Credits are deducted only for calls that produce a result. Calls that fail with an error are not charged.
Existing customers do not need to take any action. Liveform and the existing REST API and add-ons keep the same behavior, endpoints, and API keys. Use the Unit API only in the projects that need it.
Available APIs
All 14 APIs are available in every region.
Image and text analysis APIs return scores and measurements only; you decide the pass threshold. Government and bank lookup APIs summarize the authority’s answer as
verdict and verdictReason.
Getting started
- Copy the key from Unit API > Unit API key in the dashboard. The key is issued automatically when a project is created and requires the Member role or higher.
- Pick an API in API Test, run it, and check the result and the cURL example.
- Call
POST /v1/units/{api}on the host for your project’s region. Send the key in thex-api-keyheader.
Billing and usage limits
- Only calls that produce a result are charged. A call where the authority answers with a mismatch (
MISMATCH) still produced a result and is charged. Error calls with a non-200HTTP status are not charged. - Calls run from the dashboard API Test are charged under the same rules.
- Trial projects are not charged but are limited to 10 calls per month, including errors. The limit resets on the 1st of each month at 00:00 UTC.
- Per-API prices are listed in Unit API Getting Started — Billing and in the dashboard API Test.
Data retention
-
Request and response bodies are not stored. Save the result together with
txIdin your system as soon as you receive the response. -
Call records (time, API, result, error code, credits, executor,
referenceId) are kept for 3 years and are available in the dashboard call history. - Unit API Getting Started developer guide
- Errors and retries developer guide
- Unit API Reference request and response specs, code samples per language, OpenAPI spec file
Unit API menu in the dashboard
New feature A Unit API menu has been added at the bottom of the project’s left-hand menu. You can run Unit APIs without writing code and manage all call history and keys for the project.- The project status and usage limits are shown at the top of the screen (Trial projects also see this month’s usage and the next reset time).
-
The CSV includes a
referenceIdcolumn so you can find calls by your own identifier. - Unit API in the dashboard dashboard guide
Statistics page redesign — Overall, Submissions, and Unit API tabs
Improvement The Statistics page is now split into three tabs. The existing submission statistics are unchanged and live in the Submissions tab.- The Overall tab splits credits between submissions and the Unit API. Submission counts and Unit API call counts are different units and are not added together; only credits are summed.
- The Unit API tab shows call count, success rate, credits deducted, and API Test share per API, plus the top 5 API Test executors. A call you just ran takes about 20 seconds to appear.
The Overall and Submissions tabs are aggregated daily, so the previous day’s usage appears after 00:00 UTC. Unit API usage from today is available first in the Unit API tab.
- Statistics dashboard guide
ARGOS continues to improve its identity verification service for stronger security and a better user experience. Thank you for using ARGOS ID check. The ARGOS Identity team