Recharge is connected once at the org level by an admin. The credential is shared across all groups that have been granted access — individual team members don't need to connect their own accounts.
In your Recharge merchant portal, go to Tools & Apps → API tokens
Click "Create an API Token"
Give it a name (e.g. "On Belay"), set your required scopes, and click Save
Copy the token — it is only shown once
Paste it below
Ready to connect?
Go directly to the integrations page in your dashboard.
These are the data scopes On Belay can be granted for Recharge. Your org admin controls which scopes are enabled per group.
| Scope | Description | Access |
|---|---|---|
subscriptions:read | Read subscriptions | Read only |
subscriptions:write | Write subscriptions | Read / Write |
customers:read | Read customers | Read only |
customers:write | Write customers | Read / Write |
orders:read | Read orders | Read only |
charges:read | Read charges | Read only |
products:read | Read products & plans | Read only |
payment_methods:read | Read payment methods | Read only |
Double-check that you copied the full key without any leading/trailing spaces. Some platforms show a truncated preview — make sure to copy the full token. If the key was generated with restricted scopes, verify it includes the permissions listed above.
Check that your group has been granted access to this integration in On Belay → Groups → [your group] → Integrations. Also verify the specific scopes your group is permitted to use match what your query requires.
Some API keys have expiration policies. Generate a new key in Recharge and update it in On Belay → Integrations → Recharge → Update key. Consider creating a dedicated service account or machine user for On Belay so the key isn't tied to a personal account.
Still stuck? We're happy to help.
Contact support →