/magiceden/collections/pools

POST /api/magiceden/collections/pools

Price: 5 credits

List AMM (MMM) liquidity pools for a Magic Eden collection

How to use it

List the automated market maker (MMM) liquidity pools for a Magic Eden collection by its symbol (e.g. 'mad_lads'). Choose the buy side (standing bids) or sell side (asks). Each pool returns its key, type, owner, spot price in SOL, bonding curve type and delta, buy-side payment liquidity, sell-side asset count, number of buy orders, LP fee (basis points), expiry and last update time.

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)
• count integer required — Number of pools to return (min: 1)
• chain string — Blockchain (default: "solana"; one of: "solana")
• side string — Pool side: buy-side (bids) or sell-side (asks) (default: "buy"; one of: "buy", "sell")

Response

• @type string (default: "MagicedenPool")
• pool_key string required
• pool_type string nullable
• collection_symbol string nullable
• pool_owner string nullable
• spot_price number nullable
• curve_type string nullable
• curve_delta number nullable
• buyside_payment_amount number nullable
• sellside_asset_amount integer nullable
• buy_orders_amount integer nullable
• lp_fee_bp integer nullable
• expiry integer nullable
• is_mip1 boolean (default: false)
• updated_at string 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 — 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.