/magiceden/collections/search

POST /api/magiceden/collections/search

Price: 5 credits

Rank and list Magic Eden NFT collections by volume, floor price, sales or market cap

How to use it

Browse and rank Magic Eden NFT collections. Choose the ranking column (trading volume, floor price, listed count, market cap or sales), the time window (1d, 7d, 30d) and sort direction, and optionally restrict to verified collections or set minimum owner/sales thresholds. Each row returns the collection symbol, name, image, on-chain contract, floor price and its change, window and all-time volume and sales, market cap (in SOL and USD), listed count, total supply, owner count and the highest standing offer. Pass a returned symbol to the 'collections' endpoint for the full profile.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Number of collections to return (min: 1)
• chain string — Blockchain (default: "solana"; one of: "solana")
• window string — Time window for volume and sales metrics (default: "7d"; one of: "1d", "7d", "30d")
• sort string — Column to rank collections by (default: "volume"; one of: "volume", "floorPrice", "listedCount", "marketCap", "sales")
• direction string — Sort direction (default: "desc"; one of: "asc", "desc")
• verified_only boolean — Only include verified collections (default: true)
• min_owner_count integer — Minimum number of unique owners (default: 0; min: 0)
• min_sales integer — Minimum number of sales in the window (default: 0; min: 0)

Response

• @type string (default: "MagicedenCollectionRank")
• symbol string required
• name string required
• image string nullable
• contract string nullable
• floor_price number nullable
• floor_price_change number nullable
• volume number nullable
• volume_all number nullable
• volume_change number nullable
• sales integer nullable
• sales_all integer nullable
• sales_change number nullable
• market_cap number nullable
• market_cap_usd number nullable
• listed_count integer nullable
• total_supply integer nullable
• owner_count integer nullable
• unique_owner_ratio number nullable
• highest_offer number nullable
• currency string nullable
• is_verified boolean (default: false)

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 — The entity was not found, or a precondition failed 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.