/magiceden/tokens/activities

POST /api/magiceden/tokens/activities

Price: 5 credits

List the on-chain marketplace activity history of a single Magic Eden NFT

How to use it

List the marketplace activity history of a single Magic Eden NFT by its mint address, optionally filtered to a single activity type (sale, listing, delisting, bid, cancelled bid or mint). Each event returns the transaction signature, activity type, marketplace source, buyer and seller addresses, price in SOL, block time and slot.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• mint string required — Token mint address (on-chain Solana mint) (examples: "C78gKpxG69rHLdfmEiP82oA4rNXQXavTEVeEkM1S2B4P"; minLength: 1)
• count integer required — Number of activities to return (min: 1)
• chain string — Blockchain (default: "solana"; one of: "solana")
• activity_type string nullable — Filter by a single activity type (one of: "sale", "list", "delist", "bid", "cancelBid", "mint")

Response

• @type string (default: "MagicedenActivity")
• transaction_id string required
• type string nullable
• source string nullable
• collection_symbol string nullable
• mint string nullable
• name string nullable
• image string nullable
• seller string nullable
• buyer string nullable
• price number nullable
• block_time integer nullable
• slot integer nullable
• token_standard integer nullable
• rarity object nullable
  • @type string (default: "MagicedenRarity")
  • moonrank integer nullable
  • howrare integer nullable
  • me_instant integer 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.