doc.cheap

unsupported_media_type (415)

The body was sent under a content type this API does not accept, or the image in it is not a format recognition reads.

Cause

Every endpoint takes JSON. A request sent as text/plain, multipart/form-data, application/x-www-form-urlencoded or with no Content-Type at all is refused here, before the body is parsed.

The image travels as a base64 string inside a JSON object, never as a file upload. POST /v1/scans reads JPEG and PNG. A PDF, a HEIC photo, a text file or a file cut off after its first bytes is none of those. When the decoded bytes of image do not start like a JPEG or a PNG, the scan is refused here too, before recognition runs. Nothing is charged, and no free attempt of the sandbox key is spent.

The message

For the content type:

Send the request body as `Content-Type: application/json`.

For an image that is not a JPEG or PNG:

The image is not a JPEG or PNG file. Send the document photo as JPEG or PNG, base64-encoded in the `image` field.

For an image that starts like a JPEG or PNG and cannot be decoded, such as a file cut short:

The image could not be read as a JPEG or PNG file; it may be cut short or damaged. Send the document photo again as JPEG or PNG.

The fix

Send Content-Type: application/json and put the base64 image in the image field of the JSON body. Convert any other image format to JPEG before encoding it. The upload pages send quality 85 at about 1600 px on the long edge.

event_id

event_id is always null on this code. It is a refusal the caller is meant to handle, so nothing is recorded as a failure to look at. The service answers and writes one log line.

The whole catalogue, grouped by what a caller does with it, is on errors.

The response

{
  "error": {
    "code": "unsupported_media_type",
    "message": "Send the request body as `Content-Type: application/json`.",
    "docs_url": "https://doc.cheap/docs/errors/unsupported_media_type",
    "request_id": "req_9e6b1f7c-2d4a-4b83-9c51-7f0ad3e8b642",
    "event_id": null
  }
}