No-code identity workflow
Change your verification flow without a release.
Compliance changes faster than release cycles. Amani Studio lets your risk and compliance teams build journeys visually, test them in sandbox, and publish instantly - no ticket, no sprint, no deployment.
The challenge
Every threshold tweak or new market rule becomes an engineering request, so verification logic lags behind regulation and fraud trends by weeks or months.
With Amani
- Journeys built and changed by non-engineers
- Branching by country, risk tier, amount or result
- Sandbox testing before anything goes live
- Instant publishing with versioned rollback
- Engineering integrates once and stays out of the loop
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: Amani Studio, KYC, AML / Sanctions Screening, Device & IP Analysis.with Amani Skills
# Install Amani Skills once
npx -y github:AMANI-AI-ORG/skills --global
# Then ask your coding agent:
You › Set up an Amani verification workflow for our onboarding and connect the result webhook to our Node backend.
# 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();
});No-code identity workflow - common questions
Do we still need an integration?
One integration, once. After that, journey changes happen entirely in Studio without touching your code.
Can we test before publishing?
Yes - every journey runs in sandbox with test documents before you publish to production.
What if a change causes problems?
Journeys are versioned; roll back to any previous version instantly.
Related use cases
Build this flow with Amani
Compose it in Studio without code, or integrate the API in an afternoon.