# Verification Result Event

This callback event is a POST request to the specified verification callback URL and triggered when a verification has been completed and the result is known. It's used to report the verification result to the developer's backend application. This callback event is only triggered when the verification callback URL is specified in your dashboard.

Endpoint: POST VerificationResultEvent
Version: 2.0.1
Security: , 

## Request fields (application/json):

  - `status` (string, required)
    The status of the verification
    Enum: "PENDING", "SUCCESSFUL", "FAIL", "DENIED", "ABORTED", "ERROR"

  - `id` (string, required)
    The ID of the verification request.
    Example: "1234567890"

  - `event` (string, required)
    The type of the event.
    Enum: "VerificationResultEvent", "VerificationRequestEvent", "VerificationSmsDeliveredEvent"

  - `method` (string, required)
    The type of the verification.
    Enum: "sms", "flashcall", "callout", "whatsapp"

  - `identity` (object, required)
    Specifies the type of endpoint that will be verified and the particular endpoint. number is currently the only supported endpoint type.

  - `identity.type` (string, required)
    Currently only number type is supported.
    Enum: "number"

  - `identity.endpoint` (string, required)
    For type number use an [E.164](https://community.sinch.com/t5/Glossary/E-164/ta-p/7537)-compatible phone number.
    Example: "+11235551234"

  - `reference` (string)
    Used to pass your own reference in the request for tracking purposes. Must be a unique value for each started verification request. The value must be encodable in the URL path segment. This value is passed to all events and returned from the status and report endpoints. The reference can be used to check the [status of verifications](https://developers.sinch.com/docs/verification/api-reference/verification/verification-status/verificationstatusbyreference), like with ID or identity.

  - `custom` (string)
    Can be used to pass custom data in the request. Will be passed to all events. Max length 4096 characters, can be arbitrary text data.

  - `reason` (string)
    Displays the reason why a verification has FAILED, was DENIED, or was ABORTED.
    Enum: "Fraud", "Not enough credit", "Blocked", "Denied by callback", "Invalid callback", "Internal error", "Destination denied", "Network error or number unreachable", "Failed pending", "SMS delivery failure", "Invalid CLI", "Invalid code", "Expired", "Hung up without entering valid code"

  - `source` (string)
    With the SMS verification method, a user's phone number is verified by sending an SMS containing an OTP code that must be manually returned. If you are are using an Android handset, you could instead intercept the SMS message delivery and capture the OTP code automatically.
    Enum: "intercepted", "manual"


## Response 200 fields