Images

Prepare image inputs for Vardera assessment requests.

Submission guidance

Use clear, original photos where the item fills most of the frame. Avoid photos that are cropped, blurred, covered, heavily shadowed, or highly compressed. The guidance below varies by assessment type.

Coins

Submit one coin per assessment: two photos of a raw coin, its obverse and reverse; one photo showing a raw coin's obverse and reverse side by side; or one photo of a slabbed coin's front with the label in view. See Coin Assessment for detailed photo guidance.

Banknotes

Submit one note per assessment: a photo of its front, then a photo of its back, each showing the entire note with some space around it. See Banknote Assessment for more.

Cards

Submit one card per assessment request, photographed front and back. The front identifies the card and the back is needed for a grade: without a recognizable back, the assessment returns an identity and no grade. For a card in a grading holder, frame the label so its company and certificate number can be read. A holder does not hinder identification, but grading reads the card's surface through the plastic, so keep reflections and scratches on the case out of the shot. See Card Assessment for more.

Toys

Submit one toy per assessment request, with the clearest or most representative image first. Add packaging, model numbers, manufacturer marks, accessories, or condition details when they help pin down the exact collectible. See Toy Assessment for more.

Supported inputs

Assessment requests use an images array. You can supply references to previously uploaded images, reachable URLs, or base64-encoded image data.

  • Supported formats are JPEG, PNG, GIF, BMP, TIFF, WebP, ICO, HEIC, and HEIF.
  • A request can carry up to 20 images.
  • Each image must be 15 MB or less: the exact limit is 15 MiB (15,728,640 bytes), measured after base64 decoding.
  • A request to an assessment endpoint or POST /images can be up to 20 MB in total. That fits one maximum-size image as base64. To send larger or more images, upload each with POST /images and send the image_ref values, or send image URLs.

Pre-uploaded

Upload images before you request the assessment when response time matters: the assessment then reads the stored image instead of downloading it or decoding it from the request. POST /images returns an image_ref. Submit that exact reference in an assessment request from the same organization.

curl https://api.vardera.com/images \
  -H "Authorization: Bearer $VARDERA_API_KEY" \
  -F "file=@front.jpg"
{ "image_ref": "server-issued-reference.jpg" }

Use the returned image_ref as the image entry in a category assessment request:

{
  "images": [{ "image_ref": "server-issued-reference.jpg" }]
}

POST /images also accepts the URL and base64 JSON input forms described below.

Image URLs

Use image URLs when your system can host files where Vardera can fetch them during processing.

{
  "images": [{ "url": "https://example.com/front.jpg" }]
}

When the URL does not provide a reliable filename or extension, such as a signed URL, include an optional filename for Vardera to use when downloading the image:

{
  "images": [
    {
      "url": "https://example.com/download?id=123",
      "filename": "front.jpg"
    }
  ]
}

Image URLs must use http:// or https:// and be reachable by Vardera to download them in less than 30 seconds. Avoid short-lived URLs, blocked origins, or slow hosts.

Base64 data

Use base64 data to send image bytes directly. filename is required, and its extension must be one of the supported formats.

{
  "images": [
    {
      "filename": "front.jpg",
      "data": "base64-encoded-image-bytes"
    }
  ]
}

A request carrying base64 images can be up to 20 MB: one 15 MB image, or several typical phone photos. Larger requests get a 413. For more or larger images, upload them first with POST /images: the assessment request stays small, and a retry doesn't send the images again.