The Accounts API exposes the bank accounts your business holds on Rho - checking, savings, credit, treasury investment vehicles, and rewards accounts. Use it to read balances, classify activity by account type, and stitch Rho into the rest of your financial stack.
The Accounts API is part of the stable v1 contract: additive-only, with breaking changes reserved for a new API version. See Versioning and compatibility.
Every account on Rho has an account_type field that determines what it can hold and how it behaves.
| Type | Description |
|---|---|
checking | Operating cash accounts used for everyday inflows and outflows. |
savings | Higher-yield depository accounts segregated from operating cash. |
credit | Revolving credit lines backing corporate cards. |
investment | Treasury sleeves invested in money-market funds or short-duration securities. |
rewards | Cash-back balances earned on card spend. |
Account account_type is immutable for the lifetime of an account.
A GET against /api/v1/accounts returns every account in scope for your API Access Token, each with a single balance object. Balances are expressed in minor units (for example, cents for USD) alongside an ISO 4217 currency code, so treat amounts as integers rather than decimals. Alongside the balance, each account carries its type, a display name, and the masked account and routing numbers.
The list is paginated - use sort_by and order to control ordering, and follow the cursor as described in Pagination to read through businesses with many accounts. Pair with Transactions to reconcile activity against the balance.
Many integrations only care about a subset - for example, payouts only care about checking accounts. The list endpoint has no server-side type filter, so request a page of accounts and filter the returned accounts array client-side by account_type.
curl 'https://rhoapi.rho.co/api/v1/accounts?page_size=100' \
-H "Authorization: Bearer $RHO_API_TOKEN"Every transaction already carries account_id, account_type, and the account's display name, so most reconciliation needs no extra calls. When you need live balance or masked account details, fetch the account once via /api/v1/accounts/{account_id} and cache the result for the duration of the job.
Full endpoint catalogue - paths, parameters, response shapes, and required scopes - lives in the API Reference.