Verification Result Event
The Verification Result Event is triggered when a verification process has been completed and the final verification result is available.
This callback event is sent as an HTTP POST request to the verification callback URL configured in the Sinch SMV Platform.
The event is used to notify the enterprise about the outcome of the verification request.
The callback is triggered only when a verification callback URL is configured in the dashboard.
Sample Request:
{
"id": "XXXXXXXXXXXXXXXXXXXX",
"event": "VerificationResultEvent",
"method": "seamless",
"identity": {
"type": "number",
"endpoint": "+1XXXXXXXXXX"
},
"reference": "string",
"custom": "string",
"status": "PENDING",
"reason": "Expired",
"source": "intercepted"
}
| Parameter | Description | JSON Type | Required |
|---|---|---|---|
| id | Unique identifier of the verification request. This value matches the ID returned when the verification was initiated. | String | Yes |
| event | Indicates the type of callback event. For this webhook the value is always "VerificationResultEvent". | string | Yes |
| reference | Custom reference value provided when starting the verification request. Used to map the event to your internal system. | string | No |
| custom | Optional custom data that was passed when initiating the verification request. | string | No |
| identity | Contains information about the endpoint being verified (usually a phone number). | object | yes |
| type | Type of identity being verified. Currently only "number" is supported. | String | yes |
| endpoint | Type of identity being verified. Currently only "number" is supported. | string | Yes |
| method | Indicates the verification method used. (seamless) | string | yes |
| status | Indicates the final status of the verification attempt. | string | yes |
| reason | Provides additional explanation when a verification fails, is denied, or aborted. | string | yes |
| source | Indicates how the verification was completed (automatic interception or manual entry). Mostly relevant for SMS OTP flows. | string | No |
Sample Response:
The enterprise backend must return an empty 200 OK response after successfully processing the callback event.