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

# Advanced Silent Mobile Verification

`POST /mi/verification/1/verify/advanced`

## 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/advanced`
- 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

> **Deprecated.**

Verify possession of the end user's mobile phone number with a mobile network operator's data connection.
If request body is supplied with additional data, the following can be done:
- SIM swap check before the mobile phone number verification
- Fallback SMS message if silent mobile verification fails

API and URL may vary per country. Contact your Account Manager for implementation details.

## Request body

- C4fb96364cd87b1d1d15720880c5153ef26f58342e4ec03b9d5896f2251f17aeSmvVerifyAdvancedRequestDto: Silent Mobile Verification Advanced 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-advanced-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.
  - `smsFailover` C4fb96364cd87b1d1d15720880c5153ef26f58342e4ec03b9d5896f2251f17aeSmsFailoverDto: SMS failover message contents. In case this field is null, no SMS failover will be done.
    - `from` string, required: Message failover sender.
    - `text` string, required: Message failover text.
    - `validityPeriod` integer: The message validity period in seconds. When the period expires, it will not be allowed for the message to be sent.
    - `regional` C4fb96364cd87b1d1d15720880c5153ef26f58342e4ec03b9d5896f2251f17aeRegionalDto: Region specific parameters, often specified by local laws. Use this if country or region that you are sending SMS to requires some extra parameters.
      - `indiaDlt` C4fb96364cd87b1d1d15720880c5153ef26f58342e4ec03b9d5896f2251f17aeDltDto: Distributed Ledger Technology (DLT) specific parameters required for sending SMS to phone numbers registered in India.
        - `principalEntityId` string, required: Your assigned DLT principal entity ID.
        - `contentTemplateId` string: Registered DLT content template ID which matches message you are sending.
  - `simSwapCheck` C4fb96364cd87b1d1d15720880c5153ef26f58342e4ec03b9d5896f2251f17aeSimSwapCheckDto: SIM swap check parameters. In case this field is null, no SIM swap checks will be done.
    - `period` integer, required: SIM swap check will be verified with MNO in "period" amount of hours from when this request was received. The value should be greater than 0.
    - `proceedOn` C4fb96364cd87b1d1d15720880c5153ef26f58342e4ec03b9d5896f2251f17aeSimSwapProceedOnDto[]: If specified, proceed to the SMV verify in case: - SIM swap check fails - There is no SIM swap coverage - Result of the SIM swap check was unknown
  - `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` 'ACCEPTED': 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.

## 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)