Request Formats
Each Scryfall API method will return data as a JSON blob. Some methods support additional alternative formats. Each API method documents which formats it will support.
| Format | Default | Desc |
|---|---|---|
|
✓ |
Return data as a JSON blob |
|
Return data as a CSV table |
|
|
Return a formatted plaintext snippet |
|
|
Return an |
|
|
Return an |
Image and File Requests
The image and file formats will return an HTTP 302 redirect
directly to an image file or another downloadable item.
Ensure your HTTP library will accept this behavior if you use it.
Image Requests: Version
When requesting the image format, you may also provide a version parameter
for the specific image version you would like returned. It can
be small, normal, large, png, art_crop, or border_crop.
The default is large.
Image Requests: Back Face
When requesting the image format, you may also provide a face parameter
with the value back.
If this card has two faces, a redirect to an image for the back face
of the card will be returned.
If this card does not have a back face, the method will return a 404 error.
Currently the only cards with two images are those with a layout property
with the values transform or double_faced_token.
Text and Image Headers
When you request the text or image format, the API will also set
two additional HTTP headers:
| Header | Description |
|---|---|
|
A URI the Scryfall permapage for the returned card. |
|
A URI to an image of the card returned |
CSV Format Headers
When you request the csv format, the API will set these additional
additional HTTP headers:
| Header | Description |
|---|---|
|
Will have the value |
|
A URI to the next CSV page.
You can submit an HTTP |