Getting started

The Rho API gives you programmatic access to your business's banking data on Rho. Use it to pull transactions into your data warehouse, reconcile against your accounting system, power internal dashboards, or wire Rho into the workflow tools your team already runs.

Current release is read-only and covers accounts and transactions.

The API is published as v1, served under /api/v1/.

1. Create an API Access Token from your Rho banking settings. Admins and Account Owners have permission to manage API Access Tokens, and creation is protected by a 2FA challenge - see Authentication for the full lifecycle.
2. Send the token as a bearer credential on every request: Authorization: Bearer <rho_api_access_token>.
3. Walk paginated responses using the cursor returned in each page - see Pagination.

A minimal first call:

curl https://rhoapi.rho.co/api/v1/accounts \
  -H "Authorization: Bearer $RHO_API_TOKEN"

Use the sandbox environment to try the API against fictional, deterministic data before calling production:

curl https://rhoapi-sandbox.rho.co/api/v1/accounts \
  -H "Authorization: Bearer sandbox"

The sandbox accepts any non-empty bearer token, so you do not need to create a real API Access Token before testing requests there.

• Authentication - Create, send, scope, and revoke API Access Tokens. Covers IP allowlists, expiration, the 401 vs 403 distinction, and the security practices we recommend.
• Pagination - Cursor-based iteration with page_size and page_token. Includes a Python iteration example and the common pitfalls to avoid.
• Rate limits - Understand request limits, pace traffic, and retry safely after a 429 response.
• API Reference - The endpoint catalogue: paths, parameters, response shapes, and the scopes each endpoint requires.
• Versioning and compatibility - The stability contract: v1 is additive-only, what can change without a new version, and the client obligations that keep your integration working.