How it works
- A parent project holds your integration: API keys and webhook endpoints. It has no users, cards or accounts of its own.
- Each business client runs in a subproject under the parent, with its own users, cards, accounts and fees. Users, cards and accounts never move between subprojects.
- Sandbox and production each have their own parent project, with their own subprojects.
- You call the API with the parent’s API keys. Subprojects have no API keys.
Calling the API for a subproject
Name the subproject in theReap-Subproject-Id header, and authenticate with the parent’s API key:
- Every endpoint that acts on users, cards, accounts or transactions operates on a subproject and requires the header. Each endpoint page in the API reference lists the header when the endpoint accepts it.
- Webhook endpoints belong to the parent. Call them without the header.
- Each subproject has its own rate limit.
- An idempotency key applies within one subproject, so the same key sent for two subprojects does not collide.
Errors
Pausing the parent pauses every subproject under it: reads keep working, except sensitive ones such as revealing card details, cards can still be frozen, blocked or deleted and users deleted, and card authorizations are declined. See Pausing a project, and Errors for the errors every endpoint can return.
Webhooks
Events from every subproject go to the parent’s webhook endpoints. Each delivery names its subproject in theReap-Subproject-Id header, so one endpoint can route events for all your clients.
The signature covers the header. A delivery for a subproject carries a v2 signature in place of v1, so a receiver that ignores the header fails verification rather than processing an event for the wrong client. See Signature Verification.
External authorization works the same way: an authorization request for a subproject’s card goes to the parent’s REQUEST endpoint and names the subproject in Reap-Subproject-Id.