Credit

The Credit API exposes the live state of your business's credit with Rho. All three endpoints require the credit:read scope on an API Access Token.

Credit has two surfaces: credit programs, which describe the terms under which card spend is funded, and a balance, which is a point-in-time snapshot for one program. Period history for spending, repayments, and cashback is available through the Statements API.

GET /api/v1/credit-programs returns every credit program belonging to the business linked to the API Access Token.

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

{
  "credit_programs": [
    {
      "id": "81000000-0000-4000-8000-000000000001",
      "name": "Daily Credit",
      "account_id": "30000000-0000-4000-8000-000000000007",
      "repayment_cadence": "daily",
      "cashback_rate": 1.15,
      "credit_limit": {
        "amount": 25000000,
        "currency": "USD"
      }
    }
  ]
}

cashback_rate is a percentage, so 1.15 means 1.15%. Money amounts are in the currency's smallest unit, such as cents for USD.

The following fields are omitted when Rho does not have a value:

• account_id
• credit_limit
• archived_at

An active program normally omits archived_at; an archived program includes the timestamp when it was archived. repayment_cadence is daily when each day's spend is repaid the next day, or monthly when spend settles once per statement period.

GET /api/v1/credit-programs/{credit_program_id} returns one program belonging to your business.

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

Use account_id, when present, to join the program to the Accounts and Transactions APIs.

GET /api/v1/credit-programs/{credit_program_id}/balance computes a live balance snapshot. as_of identifies when the snapshot was computed.

curl "https://rhoapi.rho.co/api/v1/credit-programs/$PROGRAM_ID/balance" \
  -H "Authorization: Bearer $RHO_API_TOKEN"

{
  "credit_program_id": "81000000-0000-4000-8000-000000000001",
  "account_id": "30000000-0000-4000-8000-000000000007",
  "credit_limit": {"amount": 25000000, "currency": "USD"},
  "available_credit": {"amount": 21850000, "currency": "USD"},
  "settled_balance": {"amount": 2500000, "currency": "USD"},
  "pending_charges": {"amount": 650000, "currency": "USD"},
  "balance_due": {"amount": 1750000, "currency": "USD"},
  "balance_due_date": "2026-10-15",
  "period_start_date": "2026-09-01",
  "period_end_date": "2026-09-30",
  "as_of": "2026-09-30T12:00:00Z"
}

available_credit is the limit net of pending charges and outstanding balance. settled_balance contains settled outstanding transactions, while pending_charges contains authorized card transactions that have not settled. balance_due and the period fields describe the repayment period with an outstanding amount. account_id, balance_due_date, period_start_date, and period_end_date are omitted when unavailable.

• 400 Bad Request means a path identifier is not a UUID.
• 403 Forbidden means the API Access Token does not have credit:read.
• 404 Not Found means the program is not available to the authenticated business. Missing programs and programs belonging to another business return the same response.
• 429 Too Many Requests means the client should wait before retrying.
• 500 Internal Server Error means the program or balance could not be safely represented.
• 503 Service Unavailable means a required upstream service is temporarily unavailable.

Credit endpoints are not paginated and do not issue page tokens.

See the Rho API v1 reference for all fields and responses.