Delivery verification
Prove the right person received the delivery.
High-value and age-restricted deliveries need proof of who actually received them. Amani verifies the recipient at handover - an age check for restricted goods, an identity match for valuables - captured as evidence in seconds.
The challenge
Signature-on-glass proves nothing about who signed. Disputed deliveries, doorstep fraud and age-restricted goods reaching minors all create chargebacks and licence risk.
With Amani
- Recipient identity confirmed at the doorstep
- Age verified for alcohol, tobacco and restricted goods
- Biometric proof of delivery replaces signatures
- Disputes and chargebacks resolved with evidence
- Works offline-tolerant on courier devices
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: Age Estimation, Face Match 1:1, Liveness, ID Verification.with Amani Skills
# Install Amani Skills once
npx -y github:AMANI-AI-ORG/skills --global
# Then ask your coding agent:
You › Add an Amani age check to our web signup that only asks for ID when the estimate is near our threshold.
# 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();
});Delivery verification - common questions
Does the recipient need an account?
No - doorstep checks can run anonymously for age, or match against order identity where you hold it.
What about poor connectivity?
Capture is tolerant of intermittent connectivity, with results syncing when the device reconnects.
Is the evidence retained?
Yes - proof-of-delivery records are retained per your policy for dispute resolution.
Related use cases
Build this flow with Amani
Compose it in Studio without code, or integrate the API in an afternoon.