Account Rewards API

Per-account staking rewards and validator commissions for institutional customers.

Production API base URL: https://rewards-api.chorus.one.

Getting access

Contact Bitwise to get access to the Rewards Dashboard. Once you have access, issue and revoke API keys at https://rewards.chorus.one/api-keys.

Pass your API key in the X-API-KEY header on every request. The key implicitly scopes responses to the wallets mapped to your account, you can never see rewards for another customer's wallets even with a valid key.

Workflow

1. Call GET https://rewards-api.chorus.one/account-rewards/v1/account once to discover which wallets your key can read and the pre-built URLs for their rewards.

2. Follow the reward_urls returned from step 1 to fetch daily rewards (/v1/delegator_rewards/...) or commissions (/v1/validator_rewards/...). These URLs are public API paths, so resolve them against https://rewards-api.chorus.one.

3. Each rewards response is paginated by date. When next_url is non-null, resolve it against https://rewards-api.chorus.one to fetch the next page.

Supported networks

dYdX, Hyperliquid, Aleo.

Pagination

Rewards endpoints paginate around a 100-row target, but pages always break on a day boundary. If the 100th and 101st rows fall on the same day, the page is trimmed back so the day is not split. Consequently, a non-final page may contain fewer than 100 rows.

When more data is available, the response includes a next_url. Resolve it against https://rewards-api.chorus.one; its exact path and query format are unspecified and may change. When next_url is null, the final page has been returned.