You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: openapi-spec/external-purchases-api.yaml
+8-72Lines changed: 8 additions & 72 deletions
Original file line number
Diff line number
Diff line change
@@ -69,15 +69,13 @@ tags:
69
69
# Base URL
70
70
71
71
The base URL for the External Purchases API is `https://api.revenuecat.com/`.
72
-
72
+
73
73
# Endpoints
74
74
75
-
The API has two endpoints, `POST/receipts/external` and `POST/receipts/external/bulk`.
75
+
The API has one endpoint, `POST/receipts/external`.
76
76
77
77
`POST/receipts/external` is used for requests with a single purchase and/or payment, and processes them right away. Calling [Get Customer](/docs/api-v1#tag/customers/operation/subscribers) right after will return the updated entitlements.
78
78
79
-
`POST/receipts/external/bulk` is used only for bulk updates/imports. These updates will happen in the background and could take some time to process.
80
-
81
79
For more details check the [API reference](#operation/track-external-purchases).
82
80
83
81
## Payload
@@ -388,10 +386,9 @@ tags:
388
386
1. In the scenario when the third party payment service provider retains commissions in case of a refund, Revenuecat does not track negative revenues. Meaning, that in such cases, you will see data discrepancies with the equivalent of the commission retained by the payment service provider.
389
387
5. Entitlement identifier:
390
388
1. We support only new entitlement identifiers ([not the legacy version](/docs/integrations/webhooks/event-types-and-fields#subscription-lifecycle-events-fields)).
391
-
6. [Backfill logic](#tag/Backfill-Logic), on import transactions (using the /bulk endpoint) are not supported.
392
-
7. [Backfills](#tag/Backfill-Logic) that modify `current_period_ends_at` date, do not alter existing Events, which means that the Customer history won't reflect accurately the most up to date `expiration_at_ms`.
393
-
8. If a different `source_subscription_identifier` gets provided, doesn’t matter if it’s the same product, we can end up with concurrent transactions
394
-
9. `EXPIRATION` Events are not fired automatically. The developer needs to explicitly send a request to the External Purchases API endpoint when `status` changed to `expired`.
389
+
6. [Backfills](#tag/Backfill-Logic) that modify `current_period_ends_at` date, do not alter existing Events, which means that the Customer history won't reflect accurately the most up to date `expiration_at_ms`.
390
+
7. If a different `source_subscription_identifier` gets provided, doesn’t matter if it’s the same product, we can end up with concurrent transactions
391
+
8. `EXPIRATION` Events are not fired automatically. The developer needs to explicitly send a request to the External Purchases API endpoint when `status` changed to `expired`.
395
392
- name: External Purchases
396
393
description: Operations to track external subscriptions and purchases.
397
394
paths:
@@ -434,40 +431,6 @@ paths:
434
431
"$ref": "#/components/schemas/ExceededQuotaError"
435
432
security:
436
433
- api_key: []
437
-
"/v1/receipts/external/bulk":
438
-
tag: External Purchases
439
-
post:
440
-
tags:
441
-
- External Purchases
442
-
summary: Tracks the status of multiple external purchases
0 commit comments