Skip to main content
POST
Import a Chargebee export (customers, plans, subscriptions)
Takes the same payload as preview and performs the import, recording an idempotency mapping for every created record — re-running is safe. Subscriptions are imported in their current billing state via a direct insert: no invoice, charge, or ledger side effect, so Recurso takes over at the next renewal.

Example request

The response contains the executed plan, a created map of per-kind counts, and a failures array — per-object failures are reported there rather than aborting the whole import. After committing, prove the migration with the compare gate before cut-over.

Authorizations

Authorization
string
header
required

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

Body

application/json

The Chargebee export JSON (same shape as the preview endpoint).

customers
object[]
plans
object[]
subscriptions
object[]

Response

The commit result.

plan
object
created
object
failures
object[]