API overview - Recurr

Recurr’s public API surface is primarily an event and export contract. It exists so customers can move Recurr outcomes into their warehouse, analytics stack, support systems, finance workflows, or access model.

The API docs describe the customer integration contract. Availability, scope, and exact fields are confirmed during pilot onboarding. The full endpoint reference is published as the API reaches general availability.

What the API is for

Sending migration and Oikos events to customer systems
Exporting cohort and subscriber state
Reconciling payment and lifecycle outcomes
Supporting access continuity integrations
Backfilling or replaying events where configured

What the API is not

The API is not positioned as a replacement for Stripe, Paddle, RevenueCat, Adapty, or your own backend. Recurr fits into those systems. The customer payment rail remains the source of truth for payments. The customer access model remains the source of truth for app access.

Core concepts

Concept	Meaning
Event	A fact emitted by Recurr, such as a migration state change or lifecycle outcome
Destination	A configured endpoint or integration that receives events
Replay	A controlled resend of historical events where available
Test mode	A non-production mode for validating integration behavior

Next steps

Start with events, then review destinations and authentication.