didit-phone-verification
Integrate Didit Phone Verification standalone API to verify phone numbers via OTP. Use when the user wants to verify phones, send SMS or WhatsApp or Telegram codes, check phone verification codes, detect disposable or VoIP numbers, or implement phone-based identity verification using Didit. Supports multiple delivery channels (SMS, WhatsApp, Telegram, voice), fraud signals, and policy-based auto-decline.
Why use this skill?
Integrate Didit Phone Verification with OpenClaw. Securely verify phone numbers via SMS, WhatsApp, and Telegram with built-in fraud detection and disposable number filtering.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/rosasalberto/didit-phone-verificationWhat This Skill Does
The didit-phone-verification skill provides a robust, professional-grade interface for the Didit Phone Verification API. It enables OpenClaw to perform secure, two-step user authentication by sending time-sensitive verification codes via various channels including SMS, WhatsApp, Telegram, or voice calls. Beyond basic verification, the skill acts as a security gateway, capturing fraud signals, detecting disposable or VoIP numbers, and verifying device authenticity. By integrating this skill, you can implement high-trust identity flows that help prevent bot sign-ups, spam, and fraud while maintaining a seamless user experience. It ensures that the phone numbers provided by users are valid, accessible, and compliant with your defined security policies.
Installation
To integrate this skill into your environment, run the following command in your OpenClaw terminal:
clawhub install openclaw/skills/skills/rosasalberto/didit-phone-verification
Ensure you have obtained your x-api-key from the Didit Business Console and configured it within your environment settings to authorize the outgoing API requests.
Use Cases
- User Onboarding: Validate new user phone numbers during registration to ensure account legitimacy.
- Transaction Authorization: Require OTP verification before performing sensitive account actions or high-value financial transfers.
- Fraud Prevention: Screen users against known disposable or temporary phone number databases to block automated script attacks.
- Multi-channel Communication: Provide flexible verification options for users in different regions where specific messaging channels might be preferred.
Example Prompts
- "Verify the user +14155552671 by sending them a 6-digit WhatsApp code and save the vendor tracking data as 'registration_001'."
- "Can you check if the code '883920' provided by the user is valid for the phone number +34600000000?"
- "Send a phone verification request to +447700900000 and include the user's IP address 192.168.1.1 for fraud signal analysis."
Tips & Limitations
- Rate Limiting: Remember that each phone number is limited to 4 sends per hour. Monitor your request frequency to avoid being blocked.
- Expiration: Codes are only valid for 5 minutes. Ensure your UI informs the user of this countdown to reduce failed attempts.
- Sequence Matters: You must always call the 'Send' API before the 'Check' API for the same phone number session.
- Attempt Limits: Each code supports a maximum of 3 failed verification attempts. After 3 failures, you must trigger a new 'Send' request.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-rosasalberto-didit-phone-verification": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: external-api, data-collection
Related Skills
didit-proof-of-address
Integrate Didit Proof of Address standalone API to verify address documents. Use when the user wants to verify a proof of address, validate utility bills, bank statements, government documents, extract address from documents, verify residential address, implement address verification, or perform PoA checks using Didit. Supports OCR extraction, geocoding, name matching, and multi-page documents.
didit-aml-screening
Integrate Didit AML Screening standalone API to screen individuals or companies against global watchlists. Use when the user wants to perform AML checks, screen against sanctions lists, check PEP status, detect adverse media, implement KYC/AML compliance, screen against OFAC/UN/EU watchlists, calculate risk scores, or perform anti-money laundering screening using Didit. Supports 1300+ databases, fuzzy name matching, configurable scoring weights, and continuous monitoring.
didit-age-estimation
Integrate Didit Age Estimation standalone API to estimate a person's age from a facial image. Use when the user wants to estimate age, verify age, implement age gating, check if someone is over 18/21, perform age verification for compliance, or use facial analysis for age detection using Didit. Includes passive liveness check. Supports configurable thresholds, adaptive age estimation with ID verification fallback, and per-country age restrictions.
didit-passive-liveness
Integrate Didit Passive Liveness standalone API to verify a user is physically present. Use when the user wants to check liveness, detect spoofing attempts, verify real person presence, implement anti-spoofing, or perform passive liveness detection using Didit. Analyzes a single image without user interaction. Returns liveness score, face quality, and luminance metrics. Detects presentation attacks and duplicate faces.
didit-sessions
Integrate Didit Session & Workflow APIs — the central hub for managing verification sessions. Use when the user wants to create a verification session, set up a KYC workflow, create a session with a workflow_id, retrieve session results, get session decisions, list sessions, delete sessions, update session status, approve or decline sessions, request resubmission, generate PDF reports, share sessions between partners, import shared sessions, add or remove users from blocklist, manage blocked faces/documents/phones/emails, handle webhooks, or implement any end-to-end verification flow using Didit. Covers 11 API endpoints: create, retrieve, list, delete, update-status, generate-pdf, share, import-shared, blocklist-add, blocklist-remove, blocklist-list.