XRPL.to
GET /nft/collections/{slug}/listings/history
GET

/v1/nft/collections/{slug}/listings/history

Daily listed-count history merged with floor/volume/sales

AuthNone — works without a key

Request

GEThttps://api.xrpl.to/v1/nft/collections/fuzzybears/listings/history
Path parameterValueDescription
slugA collection slug, or its identity as issuer:taxon
Query parameterValueDescription
fromunix ms
tounix ms
curl 'https://api.xrpl.to/v1/nft/collections/fuzzybears/listings/history'

Response

200Example response5 ms · just now · 1.0 KB · 55 lines
https://api.xrpl.to/v1/nft/collections/fuzzybears/listings/history
{
  "collection": {
    "slug": "fuzzybears",
    "name": "Fuzzybears"
  },
  "points": [
    {
      "date": "2025-03-21",
      "listings": 912,
      "floor": 20,
      "volume": 17695.468614,
      "sales": 321
    },
    {
      "date": "2025-03-22",
      "listings": 932,
      "floor": 23.61864,
      "volume": 8589.362945,
      "sales": 185
    },
    {
      "date": "2025-03-23",
      "listings": 929,
      "floor": 1.96822,
      "volume": 4798.124488,
      "sales": 100
    },
    {
      "date": "2025-03-24",
      "listings": 851,
      "floor": 1.96822,
      "volume": 7712.317392,
      "sales": 106
    },
    {
      "date": "2025-03-25",
      "listings": 743,
      "floor": 1.96822,
      "volume": 8659.164528,
      "sales": 106
    }
  ],
  "summary": {
    "first": 912,
    "last": 499,
    "peak": {
      "date": "2025-03-22",
      "listings": 932,
      "floor": 23.61864,
      "volume": 8589.362945,
      "sales": 185
    },
    "days": 549
  }
}

Long arrays and strings are shortened in the example; Send request for the full answer.

What it does

Daily listed-count history merged with floor/volume/sales

A collection is its slug, or its on-chain identity as issuer:taxon. Each NFT in it comes back with its NFTokenID, the id every NFT endpoint takes. Go to NFT →
OpenAPI
PrevGET/nft/floor/history/{cid}NextGET/nft/collections/{slug}/holders/history