# POST /mi/verification/1/verify/advanced stops working

Calls to POST /mi/verification/1/verify/advanced on Infobip API stop working on January 1, 2027.

On January 1, 2027, the endpoint POST /mi/verification/1/verify/advanced will stop working and calls to it will fail. Infobip deprecated the endpoint on August 10, 2026, marking it for sunset at the start of 2027. Any integrations still targeting this path must update before the shutdown date.

## What to use instead

Verify the number using POST /mi/verification/1/verify or switch to Infobip's 2FA (SMS PIN) API. Because silent mobile verification has no direct successor, moving to an alternative verification method requires a product decision rather than just updating an endpoint.

Silent mobile verification has no named successor: moving to another verification method (POST /mi/verification/1/verify, SMS 2FA) is a product decision.

- API: Infobip API (*.api.infobip.com)
- Kind: Endpoint removal
- Announced: August 10, 2026
- Takes effect: January 1, 2027
- Calls after that day: fail
- Calls it hits: `POST /mi/verification/1/verify/advanced`
- Source: [Announcement](https://api.infobip.com/platform/1/openapi?format=json)
- Verified: November 6, 2026, against Infobip API's own pages
- Page: https://www.okapi.bot/providers/infobip-api/breaking-changes/post-mi-verification-1-verify-advanced-stops-working/

## Infobip API's words

> "deprecation":"2026-08-10T00:00:00.000+0000", "sunset":"2027-01-01T00:00:00.000+0000"

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent
