sandbox.itunes.apple.com
POST /verifyReceipt endpoint removal
Deprecated, no date
The provider has deprecated the POST /verifyReceipt endpoint without announcing a shutdown date. Subsequent calls to this endpoint will fail. This change impacts all integrations relying on receipt validation through this route.
Calls it hits
POST /verifyReceipt
What to use instead of these calls
Migrate to the App Store Server API (api.storekit.itunes.apple.com) using endpoints such as GET /inApps/v1/transactions/{transactionId} or GET /inApps/v2/history/{transactionId} to verify signed transactions, or validate receipts directly on your server following Validating receipts on the device. Switching involves more than changing an identifier, as it requires adopting an In-App Purchase key and signed JWS transactions rather than a 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 sandbox.itunes.apple.com's words
endpoint is deprecated. To validate receipts on your server, follow the steps in
Facts
- API
- sandbox.itunes.apple.com
sandbox.itunes.apple.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against sandbox.itunes.apple.com's own pages
Questions
When does this change take effect?
sandbox.itunes.apple.com deprecated POST /verifyReceipt without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: sandbox.itunes.apple.com 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.