Recurly + Bastle

Ordering is a correctness property, not an optimisation

Recurly backfill walks plans, then accounts, then subscriptions, then transactions, persisting each page as it goes. The order exists so a subscription is never written before the plan and account it points at. Occasionally a subscription references a plan the sweep did not return — usually deleted or created mid-import — and the connector fetches that plan individually rather than dropping the subscription. A silently skipped subscription is a permanently wrong MRR figure, and it is the kind of error nobody notices until a board meeting.

Signature verification

Recurly signs JSON notifications with a timestamped HMAC. Bastle recomputes it, compares in constant time, and rejects anything older than five minutes so a captured request cannot be replayed later. Where endpoint basic auth is also configured, every configured method must pass — enabling a second check never weakens the first.

Rate limits

List calls page at 200 records sorted by updated-at ascending, which is Recurly's own recommendation for a stable cursor. Rate-limited and unavailable responses honour the retry headers Recurly returns and back off up to five times rather than hammering the API, so a large import is slow before it is disruptive.

What "beta" means here

The connector is written and the inbound webhook route verifies signatures and writes normalised rows, so a connected account keeps up with changes as they happen. What is not self-serve yet is the historical backfill: the code that walks your provider's API from the beginning exists in the connector, but the scheduled runner that triggers it is still a stub, so first-time imports are run by hand with us. Expect to email someone once during setup, and expect that to stop being true.

Bastle is free while in beta, connectors included. There is no tier that unlocks a provider.