unsupported_media_type

The `Content-Type` on the request is not one this endpoint reads.

• A JSON body was sent without `Content-Type: application/json`.
• A file was posted as JSON rather than as `multipart/form-data`.
• A client library defaulted to `application/x-www-form-urlencoded`.

• Set `Content-Type: application/json` for JSON bodies.
• Use `multipart/form-data` for uploads — see the ingestion endpoints in the reference.

{
  "error": {
    "code": "unsupported_media_type",
    "message": "The `Content-Type` on the request is not one this endpoint reads",
    "request_id": "7cb7f7862a82425d8e4c3fb8a497dfe6"
  },
  "type": "https://integrable.cloud/docs/errors/unsupported_media_type",
  "title": "Unsupported Media Type",
  "status": 415,
  "detail": "The `Content-Type` on the request is not one this endpoint reads",
  "instance": "/api/bots/01a0652b-3713-7ea1-a6c9-2e895389ec34"
}

Branch on error.code, not on the message — the code is stable, the sentence is not. Log request_id either way.

Codes that are easy to confuse with this one, or that show up alongside it:

• payload_too_large

Quote the request_id from the response — hello@integrable.cloud. It is what lets us find the exact request. The full list of codes is at Error codes, and the conventions every endpoint shares are in Retries, versioning and limits.