# POST /mobile/authorization-code stops working

Calls to POST /mobile/authorization-code on Square API stopped working on December 31, 2025.

## What to use instead

Move the app from the Reader SDK to the Mobile Payments SDK, which authorizes with an OAuth access token and a location ID instead of a mobile authorization code. This transition requires more than updating an identifier, as replacing the Reader SDK with the Mobile Payments SDK is a rewrite of the app's payment flow.

Replacing the Reader SDK with the Mobile Payments SDK is a rewrite of the app's payment flow.

- API: Square API (connect.squareup.com)
- Kind: Endpoint removal
- Announced: February 20, 2025
- Takes effect: December 31, 2025
- Calls after that day: fail
- Calls it hits: `POST /mobile/authorization-code`
- Source: [Announcement](https://developer.squareup.com/docs/changelog/connect-logs/2025-02-20)
- Verified: November 6, 2026, against Square API's own pages
- Page: https://www.okapi.bot/providers/square-api/breaking-changes/post-mobile-authorization-code-stops-working/

## Square API's words

> The Mobile Authorization API is used by the Reader SDK, which is now deprecated. This API will be retired along with the Reader SDK on December 31, 2025.

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