Skip to main content

Notices · Suyeon Yang, ARGOS Identity

Introducing ID check Unit API: Pick Only the Identity Verification Checks You Need, from ID OCR to Account Holder Name Lookup
Hello, this is ARGOS Identity. We have launched Unit API for ID check. Unit API lets you call each identity verification function, such as ID document OCR, face comparison, and ID authenticity checks, on its own. There are 14 APIs in total, and they are available in every region. Until now, ID check mainly ran the full flow through Liveform, our hosted verification screen, from capturing the ID document to the final review. Now you can keep the screens you already have and add only the checks you need.

​
When you need one check, not a full verification flow

Running a service often calls for checking one specific piece of information at a specific moment, rather than a full end-to-end verification.
  • Payouts and withdrawals: Confirm that the account holder name on the payout account matches your user.
  • Seller onboarding: Confirm that a business applying to sell on your platform is currently operating.
  • Services with their own verification screens: Your screens are already built, and you only want to add ID OCR or authenticity checks.
You don’t need to build a full verification flow for each of these. Unit API was designed for exactly this: using only the checks you need, one at a time.

​
Liveform vs. Unit API

You can use both together. For example, verify users with Liveform at sign-up, then call face comparison or an ID authenticity check through Unit API when you need an extra check later.

​
The 14 Unit APIs at a glance

Unit API falls into two groups: 5 image and text analysis APIs and 9 external database lookup APIs. Analysis APIs return scores and measured values, while lookup APIs return a match result with the reason. This lets you set your own decision rules, such as “pass above a certain score,” to fit your service policy.
Example: national ID card authenticity check
The API checks whether details such as the name, ID number, and issue date match official government records, and returns the result together with the reason.

​
Where you can use Unit API

​
How to get started

  1. Get your API key: An API key is issued automatically when you create a project. Find it in the Unit API menu of your dashboard.
  2. Try it with API Test: Run any function from the dashboard before writing code. You can see the result and the credits used, and get a ready-to-use cURL example for your integration.
  3. Integrate: Results come back directly in the response, with no need to wait for a webhook.
  4. Operate: After integration, view your call history in the dashboard or download it as a CSV file. The Statistics menu shows call counts and credit usage for each API.
For integration details, see the ARGOS Developer Guide.

​
How credits and data are handled

  • You pay only for results: Credits are deducted only for calls that return a result. If an error means no result is generated, no credits are used.
  • Request and response bodies are not stored: ARGOS does not store API request or response bodies. Only call records, such as the call time and result, are kept for three years.
  • Try before you commit: Trial projects can make up to 10 calls per month without using credits, so you can test the functions before you go live.

​
Nothing changes for existing customers

After the launch of Unit API, your existing Liveform and API behavior and your authentication keys stay exactly the same. No action is required. Add Unit API whenever you need it.

​
Frequently asked questions

Q. I use Liveform. Do I need to switch to Unit API?
No. Your existing Liveform and API keep working as before. Use Unit API only when you need an extra check. Q. Can I try it before adopting it?
Yes. You can run any function with API Test in the dashboard without writing code, and trial projects can make up to 10 calls per month without using credits. Q. Are credits deducted when a call fails?
No. Credits are deducted only for calls that return a result. Q. Does ARGOS keep the ID images or personal data I send?
ARGOS does not store API request or response bodies. Only call records, such as the call time and result, are kept for three years. Q. Which regions is Unit API available in?
Unit API is available in every region.

​
Identity checks, as much as you need, when you need them

“Every business needs a different scope of identity verification at a different moment,” said Wonkyu Lee, CEO of ARGOS Identity. “With Unit API, businesses can flexibly connect the functions they need without changing their existing verification process or service flow. We will keep expanding ID check so that our customers can design identity verification around their own services and operating policies.” Wondering where Unit API fits in your service? Visit the ID check page to talk to our team. Thank you. The ARGOS Identity Team All identity verification steps in one platform. Learn more about ID check