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

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

On January 1, 2027, calls to POST /mi/verification/1/verify/synchronous will stop working and fail. Infobip deprecated this endpoint on December 24, 2025, setting its sunset for the start of 2027. Requests sent to this route will no longer be served after that date.

## What to use instead

Verify numbers using POST /mi/verification/1/verify or Infobip's 2FA SMS PIN API instead. Because silent mobile verification has no named successor, switching to another verification method requires a product decision rather than a simple endpoint swap.

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: December 24, 2025
- Takes effect: January 1, 2027
- Calls after that day: fail
- Calls it hits: `POST /mi/verification/1/verify/synchronous`
- 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-synchronous-stops-working/

## Infobip API's words

> "deprecation":"2025-12-24T00: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