App Store Server API
excludeRevoked query parameter removal on GET /inApps/v1/history/{id}
Deprecated, no dateSubscribe to App Store Server APIShare
App Store Server API deprecated the query parameter excludeRevoked without a shutdown date. This deprecation affects GET /inApps/v1/history/{id} requests that use the excludeRevoked parameter. Once removed, requests using this parameter will fail.
Calls it hits
GET /inApps/v1/history/{id}query parameter excludeRevoked
What to use instead of these calls
Send the revoked query parameter instead, and move to GET /inApps/v2/history/{transactionId}.
In App Store Server API's words
The excludeRevoked filter in Get Transaction History V1 is deprecated. Use the new revoked filter instead.
Facts
- API
- App Store Server API
api.storekit.itunes.apple.com - Kind
- Parameter removal
- Announced
- June 5, 2023
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against App Store Server API's own pages
Questions
When does this change take effect?
App Store Server API deprecated GET /inApps/v1/history/{id}, query parameter excludeRevoked without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: App Store Server 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.
More from App Store Server API 2
-
No date
GET /inApps/v1/history/{id}Endpoint removal Deprecated, no date -
No date
/documentation/AppStoreServerAPI/Get-Transaction-History-V1Removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.