moxfield.com APImoxfield.com ↗
Search Magic: The Gathering cards on Moxfield. Get card images, pricing, legalities, edition metadata, and multi-face card support via 4 endpoints.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/55189296-4a3a-4cd2-a006-802b22cd2b73/get_startup_card_images' \ -H 'X-API-Key: $PARSE_API_KEY'
Retrieves card image URLs from the Moxfield startup card list, returning the standard-resolution card image for each card.
No input parameters required.
{
"type": "object",
"fields": {
"count": "integer total number of image links discovered",
"image_links": "array of image URL strings (each is a 488x680 webp card image)"
},
"sample": {
"data": {
"count": 558,
"image_links": [
"https://assets.moxfield.net/cards/card-E02VW-normal.webp",
"https://assets.moxfield.net/cards/card-E058J-normal.webp"
]
},
"status": "success"
}
}About the moxfield.com API
The Moxfield API gives developers access to Magic: The Gathering card data across 4 endpoints, covering card images, pricing, legality information, and edition metadata. The search_card_images endpoint accepts Scryfall syntax queries and returns paginated results with per-face image URLs and dimensions. The get_card_details endpoint returns the full card object including prices, set data, and legality per format.
Card Search and Image Retrieval
The search_card_images endpoint accepts a query string using standard Scryfall syntax — operators like t:creature, c:blue, or set: codes work as expected. Results are paginated via page and page_size parameters (maximum 175 results per page). Each item in the image_links array includes a card_name, image_link URL (488×680 WebP), dimensions, and an optional face_name for double-faced or split cards. The response also returns total_cards so you can calculate total pages without an extra request.
Card Detail Data
get_card_details takes a card_id — an alphanumeric string sourced from search_card_images or discover_images results — and returns a full card object. The card field includes name, set, legalities across formats, price data, and edition variants. The endpoint also returns image_links (one URL per card face) and the dimensions string for the images. This is the primary endpoint for building card detail views or populating deck-builder card panels.
Discovery Endpoints
get_startup_card_images returns image URLs from Moxfield's curated startup card list — no parameters needed, useful for seeding a card pool or testing. discover_images goes broader, combining the startup list with type-based sweeps across creatures, artifacts, and enchantments. Its response includes a source field on each image object indicating which discovery method produced it, and total_discovered gives the deduplicated count across all sources.
Multi-Face Card Handling
Double-faced and split cards appear in search_card_images results as multiple entries within the same image_links array, distinguished by the face_name field. This applies consistently across search and detail endpoints, so transform and modal double-faced cards are handled the same way.
- Populate a deck-builder UI with card images and format legality using
get_card_details - Build a card search interface backed by Scryfall syntax queries via
search_card_images - Seed a card database with a broad image collection using
discover_images - Display per-format price data alongside card art for a collection tracker
- Handle double-faced card display by consuming the
face_namefield from search results - Paginate through large card type queries using
pageandpage_sizeto build a card gallery - Cross-reference edition variants returned in
get_card_detailsfor a set-completion tracker
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Moxfield have an official public developer API?+
How does `search_card_images` handle double-faced or transform cards?+
image_links array. The face_name field identifies which face the image corresponds to — for example, distinguishing the front and back faces of a transform card. Single-faced cards omit the face_name field.What price data is available through `get_card_details`?+
card object returned by get_card_details includes price data as part of its metadata. However, the specific pricing vendors, currencies, or foil/non-foil breakdowns surfaced depend on what Moxfield exposes per card. Historical price data and real-time price chart series are not covered by these endpoints. You can fork this API on Parse and revise it to add a dedicated pricing endpoint if your use case requires more granular price fields.Can I retrieve a user's saved decks or collection from Moxfield through this API?+
What is the maximum number of results per page in `search_card_images`?+
page_size parameter accepts a maximum value of 175. For queries matching more cards than that, use the page parameter alongside total_cards in the response to iterate through additional pages.