Clarified JWSTransactions StoreKit2 support in API v1 doc #678
+1
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation / Description
A potential customer looking to migrate to RC reached out to ask whether our https://api.revenuecat.com/v1/receipts endpoint supports JWSTransactions from StoreKit2.
I think this could be clarified in the future by adding just an explicit mention in the API docs. Maybe something like this?
➡️ For iOS, the base64-encoded receipt file (or JWSTransaction for StoreKit2); for Android, the receipt token; for Amazon, the receipt; and for Stripe, the subscription ID or the Stripe Checkout Session ID.
Changes introduced
Linear ticket (if any)
Additional comments