RevenueCat Purchases API
v1 receipt validation and transaction lifecycle operations.
RevenueCat Purchases API is one of 12 APIs that RevenueCat publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Purchases. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes 3 operations across 3 paths, and defines 4 schemas. It is described by OpenAPI 3.0.1, at version 1.0.
Requests are made against 2 base URLs: https://api.revenuecat.com/v1, https://api.revenuecat.com/v2.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
RevenueCat Purchases API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (bearerAuth).
bearerAuth— RevenueCat API key passed as an HTTP Bearer token. v1 accepts public (client) or secret (server) keys; v2 uses dedicated v2 API keys.
Paths & Operations 3
Across 3 paths, the API surfaces 3 operations — 3 POST. Each is listed below with its method, path, parameters, and response codes.
v1 receipt validation and transaction lifecycle operations.
Schemas 4
The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Subscriber (8 properties), ReceiptRequest (7 properties), EntitlementInfo (3 properties), SubscriberResponse (3 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from RevenueCat 11
Other APIs RevenueCat publishes across the network.