Skip to main content
POST
Compare gate — prove the RevenueCat migration before cut-over
Diffs the uploaded RevenueCat export (the same JSON the commit consumed) against the tenant’s live Recurso data with zero writes: coverage (subscribers with an email, active entitlements), fidelity (product price, currency, period; identity), and billing continuity — an entitlement whose expires_at drifted more than an hour from the imported period end is flagged. ready: true means zero issues. Each run is persisted as a citable compare report.

Example request

Example response

Authorizations

Authorization
string
header
required

Tenant API key obtained from POST /auth/register or POST /v1/developer/keys.

Body

application/json

The same RevenueCat export JSON the commit consumed.

subscribers
object[]
products
object[]

Response

The compare report.

source
string
customers
object

Migration-compare coverage for one record kind.

plans
object

Migration-compare coverage for one record kind.

subscriptions
object

Migration-compare coverage for one record kind.

issues
object[]
ready
boolean
generated_at
string<date-time>