API reference / KYC / Identity
Mobile ownership: send OTP
Sends an OTP to the number and returns the reference_id, proving the person holds the number against the telco record.
POST
/v1/verify/mobile/otp- Authentication
- Bearer token
- Scope
kyc:verify
Before you integrate
- This is step 1 of 2. The person receives the OTP on the number; call /v1/verify/mobile/otp/verify with the same mobile, this reference_id and the OTP to finish.
- Each call is charged separately. This proves the person holds the number against the telco record.
Request body
| Field | Type | Required | Description |
|---|---|---|---|
mobile | string | Yes | 10-digit Indian mobile number starting 6 to 9; a leading +91, 91 or 0 and spaces are ignored. |
Sample code
Set your key in the GRAPPI_API_KEY environment variable. Sample values are placeholders.
curl -sS -X POST 'https://grappi.ai/v1/verify/mobile/otp' \
-H "Authorization: Bearer $GRAPPI_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"mobile": "9876543210"
}'Sample response
{
"request_id": "req_01HZY3K8M2",
"result": {
"reference_id": "telecom_abc123"
}
}Response fields
| Field | Type | Description |
|---|---|---|
reference_id | string | Reference for this OTP. Send it back, with the OTP the person receives, to /v1/verify/mobile/otp/verify. |
Errors
Every failure has the same shape. A call that fails on our side or at the data source is refunded to your wallet; a "no record found" answer is charged. See the error reference.