---
title: "Silent Mobile Verification"
method: POST
path: "/mi/verification/1/verify"
tags: ["connectivity", "mobile-identity", "identity-verification"]
---

# Silent Mobile Verification

`POST /mi/verification/1/verify`

## Request

- Base URL: `https://api.infobip.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.infobip.com/mi/verification/1/verify`
- Auth: one of:
  - OAuth 2
    - Client credentials
    - Token URL: `https://api.infobip.com/auth/1/oauth2/token`
  - API key in header `Authorization`
  - API key in header `Authorization`
  - HTTP basic

Verify possession of end-user's mobile phone number with the mobile network operator's data connection.
API and URL may vary per country. Please contact your sales for more details.

## Request body

- C4fb96364cd87b1d1d15720880c5153ef26f58342e4ec03b9d5896f2251f17aeSmvVerifyRequestDto: Silent Mobile Verification request object.
  - `consentGranted` boolean, required: Indicates whether you have consent from mobile phone number's owner to perform this request. All requests that do not have this property set to "true" will be rejected.
  - `phoneNumber` string, required: Mobile phone number (MSISDN) to verify. The number must be in international format.
  - `callbackUrl` string, required: Your URL that will be called to provide [result](#platform-connectivity/mobile-identity/receive-silent-mobile-verification-result) when the process is completed.
  - `returnUrl` string: An URL to which the mobile device will be redirected to when verification is complete.
  - `deviceIp` string, xxx.xxx.xxx.xxx|xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx: IPv4 or IPv6 address of the mobile device that will be verified with operator. Currently, can be used only in Brazil.
  - `devicePort` integer: Port of the mobile device that will be verified with operator. Can be used only when "deviceIp" is also provided. Currently, can be used only in Brazil.

## Response `200`

OK

- object
  - `status` 'REDIRECT': Silent Mobile Verification request status.
  - `token` string, uuid: Unique request ID. The whole flow from the request to response has same token so it can be used for debugging in case of error or matching API request with the callback webhook response.
  - `deviceRedirectUrl` string, uri: An URL to perform mobile device redirect to if specified so by 'status'.

## Other responses

- `400`: Bad request
- `401`: Unauthorized - Platform authentication error
- `403`: Permission denied - Platform authorization error
- `422`: Unprocessable content
- `500`: Internal server error

---

[API](https://skmtc.dev/infobip/apis/infobip-openapi-specification.md) - [All operations](https://skmtc.dev/infobip/apis/infobip-openapi-specification/llms.txt) - [OpenAPI document](https://skmtc.dev/infobip/apis/infobip-openapi-specification/revisions/9dcbbaf902de?raw)