POST /api/magiceden/wallets/tokens
Price: 5 credits
List the NFTs held by a wallet on Magic Eden (Solana)
List the NFTs held by a Solana wallet, as indexed by Magic Eden. Each token returns its mint address, name, image, parent collection symbol and name, whether it is currently listed (with price in SOL and listing type), last sale price, traits, creators and rarity ranks.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)address string required — Wallet address (on-chain Solana account) (examples: "4QZKsNk1ucKqy8LXUGu9TBs76abXMCgRWMNHUPf6LLjC"; minLength: 1)count integer required — Number of tokens to return (min: 1)chain string — Blockchain (default: "solana"; one of: "solana")@type string (default: "MagicedenToken")mint string requiredname string nullableimage string nullableanimation_url string nullablemedia_category string nullablecollection_symbol string nullablecollection_name string nullableowner string nullableprice number nullablelisting_type string nullableis_listed boolean (default: false)listing_updated_at string nullablelast_sale_price number nullableseller_fee_basis_points integer nullabletoken_standard integer nullablesupply integer nullableis_tradeable boolean (default: false)is_frozen boolean (default: false)update_authority string nullableescrow_pubkey string nullableexternal_url string nullableattributes array (default: [])@type string (default: "MagicedenTokenAttribute")trait_type string requiredvalue string requiredcreators array (default: [])@type string (default: "MagicedenCreator")address string requiredshare integer (default: 0)is_verified boolean (default: false)rarity object nullable@type string (default: "MagicedenRarity")moonrank integer nullablehowrare integer nullableme_instant integer nullable422 — 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.