---
title: "List historical rewards"
method: GET
path: "/v1/networks/{network}/rewards"
tags: ["Primary Network Rewards"]
---

# List historical rewards

`GET /v1/networks/{network}/rewards`

Lists historical rewards on the Primary Network for the supplied addresses.

## Path parameters

- `network` 'mainnet' | 'fuji' | 'testnet', required

## Query parameters

- `addresses` string
- `pageToken` string
- `pageSize` integer
- `nodeIds` string
- `sortOrder` 'asc' | 'desc'
- `currency` 'usd' | 'eur' | 'aud' | 'cad' | 'chf' | 'clp' | 'cny' | 'czk' | 'dkk' | 'gbp' | 'hkd' | 'huf' | 'jpy' | 'nzd' — ISO 4217 currency code.

## Response `200`

Successful response

- ListHistoricalRewardsResponse
  - `nextPageToken` string — A token, which can be sent as `pageToken` to retrieve the next page. If this field is omitted or empty, there are no subsequent pages.
  - `historicalRewards` HistoricalReward[], required
    - `addresses` string[], required — An array of P-Chain wallet addresses.
    - `txHash` string, required
    - `amountStaked` string, required — Amount staked by the validator this reward comes from. For autoRenewed validators this is the position's compounded weight, so it is the same on every cycle rather than the weight held during that particular cycle — per-cycle weight is not recorded on chain.
    - `nodeId` string, required
    - `startTimestamp` number, required
    - `endTimestamp` number, required
    - `rewardType` 'VALIDATOR' | 'DELEGATOR' | 'VALIDATOR_FEE', required
    - `stakingType` 'fixed' | 'autoRenewed', required — Staking kind. `autoRenewed` type validators run in repeating cycles; for these the top-level startTimestamp/endTimestamp/amountStaked reflect the current cycle and compounded weight.
    - `utxoId` string, required
    - `outputIndex` number, required
    - `reward` AssetWithPriceInfo, required
      - `assetId` string, required — Unique ID for an asset.
      - `name` string, required — Name of this asset.
      - `symbol` string, required — Symbol for this asset (max 4 characters).
      - `denomination` number, required — Denomination of this asset to represent fungibility.
      - `type` 'secp256k1' | 'nft', required — Type of asset like SECP256K1 or NFT.
      - `amount` string, required — Amount of the asset.
      - `historicalPrice` Money
        - `currencyCode` 'usd' | 'eur' | 'aud' | 'cad' | 'chf' | 'clp' | 'cny' | 'czk' | 'dkk' | 'gbp' | 'hkd' | 'huf' | 'jpy' | 'nzd', required — ISO 4217 currency code.
        - `value` number, required — Monetary value in base 10 decimals.
    - `rewardTxHash` string, required

## Other responses

- `400` — Bad requests generally mean the client has passed invalid or malformed parameters. Error messages in the response could help in evaluating the error.
- `401` — When a client attempts to access resources that require authorization credentials but the client lacks proper authentication in the request, the server responds with 401.
- `403` — When a client attempts to access resources with valid credentials but doesn't have the privilege to perform that action, the server responds with 403.
- `404` — The error is mostly returned when the client requests with either mistyped URL, or the passed resource is moved or deleted, or the resource doesn't exist.
- `429` — This error is returned when the client has sent too many, and has hit the rate limit.
- `500` — The error is a generic server side error that is returned for any uncaught and unexpected issues on the server side. This should be very rare, and you may reach out to us if the problem persists for a longer duration.
- `502` — This is an internal error indicating invalid response received by the client-facing proxy or gateway from the upstream server.
- `503` — The error is returned for certain routes on a particular Subnet. This indicates an internal problem with our Subnet node, and may not necessarily mean the Subnet is down or affected.

---

[API](https://skmtc.net/avax/apis/data-api.md) · [All operations](https://skmtc.net/avax/apis/data-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/avax/data-api/revisions/745a94fa47f5/schema)