Phone Verification
Verify numbers. Catch burners and SIM swaps.
A phone number is an identity signal - if you interrogate it. Amani validates the number with carrier data, flags VoIP and burner ranges, detects recent SIM swaps, and confirms possession with OTP when you want it.
Capabilities
What Phone Verification gives you.
Carrier lookup
Line type, carrier and status straight from network data - dead numbers rejected instantly.
VoIP & burner detection
Virtual and disposable ranges flagged before they become throwaway accounts.
SIM-swap signals
Recent SIM changes surfaced so OTPs aren’t sent into an attacker’s hands.
Optional OTP
Possession confirmed by SMS or voice code, only on the journeys that need it.
Identity match
Where carrier data allows, the subscriber name is matched to the verified identity.
Global numbering
Validation and formatting for numbering plans in every country.
From session to signed result.
Four steps - the same integration pattern as every Amani module.
Create a session
One API call (or a Studio journey) starts a verification session for this module.
User completes the flow
Your customer is guided through capture in your branded UI - web or mobile.
Checks run in real time
Phone Verification executes alongside any other modules in the journey.
You receive a signed result
A webhook delivers the decision, scores and evidence to your backend.
For developers
Integrate Phone Verification.
Authenticate, create a profile, generate a verification URL - then let Amani handle the rest. Or describe what you want to your AI coding agent and let Amani Skills wire it up from the live docs.
Available on
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"
}'
# Phone Verification runs inside this session - configure it in Amani Studio.with Amani Skills
# Install Amani Skills once
npx -y github:AMANI-AI-ORG/skills --global
# Then ask your coding agent:
You › Verify the customer’s phone number with Amani during signup in 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();
});Phone Verification - common questions
Do I have to send an OTP?
No - the risk lookup runs silently. Add OTP only where possession matters, like account recovery or payout changes.
What does SIM-swap detection prevent?
Account-takeover via hijacked numbers: a recent swap on file lets you hold OTP-based actions until the number is trusted again.
Can it run inside a KYC flow?
Yes - phone checks slot into any Studio journey and their signals feed the overall session risk score.
Related modules
Add Phone Verification to your flow
Switch it on in Amani Studio, or call it directly from the API.