Airtel Failure Response
Header Enrichment API
Responses
For 302 HTTP response code, the following values will be present in the result query parameter.
| Code | Description |
|---|---|
| SUCCESS | Request processed successfully |
| INVALID_TOKEN_CONTEXT | Unable to parse H.E. headers |
| USER_NOT_AUTHENTICATED_BY_MOBILE_NETWORK | Unable to perform H.E. / Invalid details in H.E. |
| INVALID_ARGUMENT | Invalid request parameter passed / Duplicate state passed |
| SUB_ACCOUNT_NOT_FOUND | Invalid sub_acc_id passed |
| PERMISSION_DENIED | Number Verification service is disabled |
HTTP 400 Response
| Code | Description |
|---|---|
| BAD_REQUEST | Redirect URI is invalid or not as per configuration |
Verification API
(Server-to-Server, HMAC Authentication)
To be handled by Sinch.
| Parameter | Data Type | Description | Mandatory |
|---|---|---|---|
| success | Boolean | False (Error Case) | Yes |
| state | String | Request unique ID to maintain state between the Device Binding API and UPI App Backend redirect URI | Yes |
| request_id | String | Request ID shared by Airtel to trace failed requests | For failure cases only |
| message | String | Failure message | For failure cases only |