Verification by country
Open a new market in one click.
Expanding into a new market should not mean a new vendor and a new integration. Amani already covers documents from 220+ countries - switch the market on, apply local rules, and start verifying the same day.
The challenge
Each market brings different documents, languages, data sources and regulatory expectations. Sourcing a local provider per country multiplies contracts, integrations and compliance overhead.
With Amani
- Documents from 220+ countries and territories supported
- Local-language OCR and transliteration handled
- Per-market journeys with country-specific rules
- Local data sources used automatically where available
- One contract and one integration across every market
The stack
Modules powering this flow.
Switch these on in Amani Studio - or call them directly from one API.
For developers
Build this flow.
Three API calls start the session; the modules above run inside it. Compose the journey in Amani Studio without code, or let your AI coding agent wire up the SDK from a single prompt.
- JWT auth with refresh tokens
- Regional base URLs (EU · TR · UAE)
- HMAC-signed webhooks with retries
- 27 languages in the SDKs
verify.sh
# 1 · Authenticate (server-side only)
curl -X POST 'https://ae.amani.ai/api/v2/user/login/' \
--form 'username="you@company.com"' \
--form 'password="••••••••"'
# 2 · Create the customer profile
curl -X POST 'https://ae.amani.ai/api/v2/profile' \
-H 'Authorization: Bearer $ACCESS_TOKEN' \
--form 'id_card_number="784199012345678"' \
--form 'name="Layla Haddad"'
# 3 · Generate the verification URL
curl -X POST 'https://ae.amani.ai/api/v2/profile/url' \
-H 'Authorization: Bearer $ACCESS_TOKEN' \
-H 'Content-Type: application/json' \
--data '{
"profile": PROFILE_ID,
"web_sdk_url": "https://verify.amani.ai",
"language": "en",
"return_url": "https://yourapp.com/verified"
}'
# This session runs: ID Verification, KYC, Database Validation, Amani Studio.with Amani Skills
# Install Amani Skills once
npx -y github:AMANI-AI-ORG/skills --global
# Then ask your coding agent:
You › Add the Amani KYC UI SDK to our Android onboarding right after sign-up, with ID document capture enabled.
# The matching skill fetches the live docs, pins the
# current SDK version and wires up the integration -
# secrets left as placeholders. Claude Code, Cursor and
# any Agent-Skills-compatible tool.webhooks.ts
// Amani signs every webhook with an HMAC signature using
// your secret. Always verify it before processing.
import crypto from 'node:crypto';
app.post('/webhooks/amani', (req, res) => {
// Confirm the exact header name in the Webhooks API reference.
const signature = req.get('X-Amani-Signature') ?? '';
const expected = crypto
.createHmac('sha256', process.env.AMANI_WEBHOOK_SECRET)
.update(req.rawBody)
.digest('hex');
const valid =
signature.length === expected.length &&
crypto.timingSafeEqual(Buffer.from(signature), Buffer.from(expected));
if (!valid) return res.status(401).end();
const { profile, status } = req.body;
if (status === 'approved') activateAccount(profile);
res.status(200).end();
});Verification by country - common questions
How do we configure rules per country?
Amani Studio branches journeys by detected country, so each market gets its own document requirements, checks and thresholds.
Is coverage the same everywhere?
Document coverage is global; database and registry coverage is deepest in the GCC, Türkiye, UK and EU. We can share the current source matrix for your markets.
Do we need separate contracts per market?
No - one agreement covers every country you verify in.
Related use cases
Build this flow with Amani
Compose it in Studio without code, or integrate the API in an afternoon.