/magiceden/collections/stats

POST /api/magiceden/collections/stats

Price: 1 credit

Get aggregated market statistics for a Magic Eden collection

How to use it

Get aggregated market statistics for a Magic Eden collection by its symbol (e.g. 'mad_lads'). Returns floor price, listed count, highest standing offer, trading volume over 24h/7d/30d/all-time, sales counts over 24h/7d/30d, 24h average price, and floor price change over 24h/7d/30d. All prices are in SOL.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• symbol string required — Collection symbol (its human-readable alias, e.g. 'mad_lads') (examples: "mad_lads", "okay_bears"; minLength: 1)
• chain string — Blockchain (default: "solana"; one of: "solana")

Response

• @type string (default: "MagicedenCollectionStats")
• symbol string required
• floor_price number nullable
• listed_count integer nullable
• highest_offer number nullable
• volume_24h number nullable
• volume_7d number nullable
• volume_30d number nullable
• volume_all number nullable
• sales_24h integer nullable
• sales_7d integer nullable
• sales_30d integer nullable
• avg_price_24h number nullable
• floor_change_24h number nullable
• floor_change_7d number nullable
• floor_change_30d number nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Collection not found Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.