POST /verifyReceipt → endpoint removal
App Store Receipts API
Deprecated, no date
The provider has deprecated the POST /verifyReceipt endpoint without announcing a shutdown date. Calls directed to this endpoint will eventually fail once it is removed. The change affects any integration relying on legacy receipt verification.
Calls it hits
POST /verifyReceipt
What to use instead of these calls
Use the App Store Server API, such as GET /inApps/v1/transactions/{transactionId} or GET /inApps/v2/history/{transactionId}, and verify signed transactions, or validate receipts on your server following Validating receipts on the device. Moving off verifyReceipt requires more than changing an identifier, as it involves adopting an In-App Purchase key and signed JWS transactions instead of the shared secret.
Moving off verifyReceipt means adopting the App Store Server API, with an In-App Purchase key and signed (JWS) transactions instead of the shared secret.
In App Store Receipts API's words
endpoint is deprecated. To validate receipts on your server, follow the steps in
Facts
- API
- App Store Receipts API
buy.itunes.apple.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against App Store Receipts API's own pages
Questions
When does this change take effect?
App Store Receipts API deprecated POST /verifyReceipt without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: App Store Receipts API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.