# Get RedStone payload

> RedStone's latest signed packages, as the payload the band's writePrices verifies.

Source: https://docs.tapehouse.xyz/api/get-red-stone-payload

`GET /v1/redstone/payload`

Read from RedStone's keyed gateways, then its public ones, so no client needs a key. Each data package is served only with the band's three signatures that recover to redstone-primary-prod's signers, all at one timestamp. `payload` is what an SDK's `PackageSource` returns for the same IDs.

## Query parameters

- `feeds` (required): Data package IDs separated by commas, a single feed such as `NVDA---24_7` or a group such as `NY_MARKET_STATUS`.

## Response

- `timestampMs` (integer)
- `payload` (hex)
- `packages` (object[])
  - `dataPackageId` (string)
  - `signer` (address)
  - `timestampMs` (integer)
  - `dataPoints` (object[])
    - `dataFeedId` (string)
    - `value` (integer string)

## Example

```bash
curl "https://indexer-production-f5dc.up.railway.app/v1/redstone/payload?feeds=TSLA---24_7"
```

## Errors

- 400: Why the request was not served.
- 401: An X-API-Key the operator did not issue.
- 402: Over the public tier's rate, where the operator sells the requests beyond it. The `PAYMENT-REQUIRED` header is the base64 of a JSON document of x402's version 2: what a request costs in USDG, and to whom, on which chain. Repeat the request with `PAYMENT-SIGNATURE`, the base64 of the payment signed for it; it is served once the payment settles, and its `PAYMENT-RESPONSE` header is the settlement.
- 429: Over the tier's rate.
- 503: Why the request was not served.