Jio Failure Response
Device Binding
Failure response is of two types:
a. Validation Failure Response
In case of validation failure, return JSON response.
Example:
{
"success": false,
"errors": [
{
"reason": "error",
"details": "error description"
}
]
}
| Parameter | Data Type | Description | Mandatory |
|---|---|---|---|
| success | Boolean | False (Error Case) | Yes |
| errors[0].reason | String | Error reason | Yes |
| errors[0].details | String | Error description | Yes |
b. Redirect URL Failure Response
In case of other failures, the error is returned to the redirect URL of the UPI App Backend.
To be handled by Sinch.
URL Format
<UPIApp-Backend-Redirect-URL>?result=<error_code>&state=<state-parameter-received-in-request>&description=<description-of-error>
Sample Failure URL
<UPIApp-Backend-Redirect-URL>?result=INVALID_MSISDN&state=7018cfa9-75ba-4e16-8015
| Parameter | Data Type | Description | Mandatory |
|---|---|---|---|
| state | String | State parameter received in Device Binding API request | Yes |
| result | String | Error code (for example: INVALID_MSISDN) | Yes |
| description | String | Description of error | Yes |
Signature Verify API
Error Response Body Parameters.
To be handled by Sinch.
| Parameter | Data Type | Description | Mandatory |
|---|---|---|---|
| success | Boolean | False (Error Case) | Yes |
| errors[0].reason | String | Error reason | Yes |
| errors[0].details | String | Error description | Yes |
| state | String | Request unique ID to maintain state between the Device Binding API and UPI App Backend redirect URI | Yes |
Common Error Response Codes From Jio
| HTTP Status Code | Code Returned to Partner |
|---|---|
| 401 | INVALID_CLIENT |
| 403 | ACCESS_DENIED |
| 400 | INVALID_REQUEST |
| 500 | SERVER_ERROR |