---
title: "Get verification by Reference"
method: GET
path: "/verification/v1/verifications/reference/{reference}"
tags: ["Verification status"]
---

# Get verification by Reference

`GET /verification/v1/verifications/reference/{reference}`

Queries the verification result by sending the verification Reference. With this query you can get the result of a verification.

## Response `200`

A success response, or an [Error](https://developers.sinch.com/docs/verification/api-reference/errors/).

- union
  - object
    - `id` string — The unique ID of the verification request.
    - `status` 'PENDING' | 'SUCCESSFUL' | 'FAIL' | 'DENIED' | 'ABORTED' | 'ERROR' — The status of the verification
    - `reason` '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' — Displays the reason why a verification has `FAILED`, was `DENIED`, or was `ABORTED`.
    - `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.
    - `identity` Identity — Specifies the type of endpoint that will be verified and the particular endpoint. `number` is currently the only supported endpoint type.
      - `type` 'number', required — Currently only `number` type is supported.
      - `endpoint` string, required — For type `number` use an [E.164](https://community.sinch.com/t5/Glossary/E-164/ta-p/7537)-compatible phone number.
    - `countryId` string — The ID of the country to which the verification was sent.
    - `verificationTimestamp` string — The timestamp in UTC format. <br> **Note:** The formatting does not respect `ISO-8601` and the returned value has the format `YYYY-MM-DDThh:mm:ss.SSS`. If you need to parse this value into a specific date object in your programming language, please append `Z` (Zulu time = UTC) at the end of the date value to match the `ISO-8601` format: `YYYY-MM-DDThh:mm:ss.SSSZ`.
    - `method` 'sms' — The method of the verification request. This will always be `sms`.
    - `price` object — Prices associated with this verification
      - `verificationPrice` VerificationPrice
        - `currencyId` string — ISO 4217 currency code
        - `amount` number, float
    - `source` 'intercepted' | 'manual' — 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.
  - object
    - `id` string — The unique ID of the verification request.
    - `status` 'PENDING' | 'SUCCESSFUL' | 'FAIL' | 'DENIED' | 'ABORTED' | 'ERROR' — The status of the verification
    - `reason` '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' — Displays the reason why a verification has `FAILED`, was `DENIED`, or was `ABORTED`.
    - `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.
    - `identity` Identity — Specifies the type of endpoint that will be verified and the particular endpoint. `number` is currently the only supported endpoint type.
      - `type` 'number', required — Currently only `number` type is supported.
      - `endpoint` string, required — For type `number` use an [E.164](https://community.sinch.com/t5/Glossary/E-164/ta-p/7537)-compatible phone number.
    - `countryId` string — The ID of the country to which the verification was sent.
    - `verificationTimestamp` string — The timestamp in UTC format. <br> **Note:** The formatting does not respect `ISO-8601` and the returned value has the format `YYYY-MM-DDThh:mm:ss.SSS`. If you need to parse this value into a specific date object in your programming language, please append `Z` (Zulu time = UTC) at the end of the date value to match the `ISO-8601` format: `YYYY-MM-DDThh:mm:ss.SSSZ`.
    - `method` 'flashcall' — The method of the verification request. This will always be `flashcall`.
    - `callComplete` boolean — Shows whether the call is complete or not.
    - `callResult` 'ANSWERED' | 'CANCEL' | 'COMPLETED' | 'NO_ANSWER' | 'BUSY' | 'FAILED' — The type of the call result.
    - `price` StatusPrice — Prices associated with this verification
      - `verificationPrice` VerificationPrice
        - `currencyId` string — ISO 4217 currency code
        - `amount` number, float
      - `terminationPrice` TerminationPrice
        - `currencyId` string — ISO 4217 currency code
        - `amount` number, float
      - `billableDuration` integer — The time of the call for which the fee was charged. Present only when termination debiting is enabled (disabled by default). Depending on the type of rounding used, the value is the actual call time rounded to the nearest second, minute or other value.
    - `source` 'intercepted' | 'manual' — 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.
  - object
    - `id` string — The unique ID of the verification request.
    - `status` 'PENDING' | 'SUCCESSFUL' | 'FAIL' | 'DENIED' | 'ABORTED' | 'ERROR' — The status of the verification
    - `reason` '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' — Displays the reason why a verification has `FAILED`, was `DENIED`, or was `ABORTED`.
    - `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.
    - `identity` Identity — Specifies the type of endpoint that will be verified and the particular endpoint. `number` is currently the only supported endpoint type.
      - `type` 'number', required — Currently only `number` type is supported.
      - `endpoint` string, required — For type `number` use an [E.164](https://community.sinch.com/t5/Glossary/E-164/ta-p/7537)-compatible phone number.
    - `countryId` string — The ID of the country to which the verification was sent.
    - `verificationTimestamp` string — The timestamp in UTC format. <br> **Note:** The formatting does not respect `ISO-8601` and the returned value has the format `YYYY-MM-DDThh:mm:ss.SSS`. If you need to parse this value into a specific date object in your programming language, please append `Z` (Zulu time = UTC) at the end of the date value to match the `ISO-8601` format: `YYYY-MM-DDThh:mm:ss.SSSZ`.
    - `method` 'callout' — The method of the verification request. This will always be `callout`.
    - `callComplete` boolean — Shows whether the call is complete or not.
    - `callResult` 'ANSWERED' | 'CANCEL' | 'COMPLETED' | 'NO_ANSWER' | 'BUSY' | 'FAILED' — The type of the call result.
    - `price` StatusPrice — Prices associated with this verification
      - `verificationPrice` VerificationPrice
        - `currencyId` string — ISO 4217 currency code
        - `amount` number, float
      - `terminationPrice` TerminationPrice
        - `currencyId` string — ISO 4217 currency code
        - `amount` number, float
      - `billableDuration` integer — The time of the call for which the fee was charged. Present only when termination debiting is enabled (disabled by default). Depending on the type of rounding used, the value is the actual call time rounded to the nearest second, minute or other value.
  - object
    - `id` string — The unique ID of the verification request.
    - `status` 'PENDING' | 'SUCCESSFUL' | 'FAIL' | 'DENIED' | 'ABORTED' | 'ERROR' — The status of the verification
    - `reason` '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' — Displays the reason why a verification has `FAILED`, was `DENIED`, or was `ABORTED`.
    - `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.
    - `identity` Identity — Specifies the type of endpoint that will be verified and the particular endpoint. `number` is currently the only supported endpoint type.
      - `type` 'number', required — Currently only `number` type is supported.
      - `endpoint` string, required — For type `number` use an [E.164](https://community.sinch.com/t5/Glossary/E-164/ta-p/7537)-compatible phone number.
    - `countryId` string — The ID of the country to which the verification was sent.
    - `verificationTimestamp` string — The timestamp in UTC format. <br> **Note:** The formatting does not respect `ISO-8601` and the returned value has the format `YYYY-MM-DDThh:mm:ss.SSS`. If you need to parse this value into a specific date object in your programming language, please append `Z` (Zulu time = UTC) at the end of the date value to match the `ISO-8601` format: `YYYY-MM-DDThh:mm:ss.SSSZ`.
    - `method` 'whatsapp' — The method of the verification request. This will always be `whatsapp`.
    - `price` object — Prices associated with this verification
      - `verificationPrice` VerificationPrice
        - `currencyId` string — ISO 4217 currency code
        - `amount` number, float
    - `source` 'intercepted' | 'manual' — 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.

---

[API](https://skmtc.net/sinch/apis/verification-sinch.md) · [All operations](https://skmtc.net/sinch/apis/verification-sinch/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/sinch/verification-sinch/revisions/bbeffc72789a/schema)