Skip to main content
General·HTTP 415·API

Unsupported media type

unsupported_media_type

The request's Content-Type is not one this endpoint accepts.

What this means​

The body was sent with a Content-Type header the endpoint does not read, or with none. Most endpoints accept application/json.

How to fix it​

Set the Content-Type header to the type the API reference gives for the endpoint, and send the body in that form.

Retry behavior​

Sending the same request again gets the same answer.

How it appears in the response​

ComputeSphere returns errors as RFC 7807 Problem Details. The type field is the docs URL for this page — switch on code in your client.

{
  "type":    "https://docs.computesphere.com/errors/unsupported_media_type",
  "title":   "Unsupported media type",
  "status":  415,
  "code":    "unsupported_media_type",
  "detail":  "The request's Content-Type is not one this endpoint accepts.",
  "instance": "/v2/…",
  "request_id": "f47ac10b-58cc-4372-a567-0e02b2c3d479",
  "trace_id":   null
}

The Content-Type header is application/problem+json. On field-level validation errors a non-empty errors[] array also appears, each entry carrying its own docs_url for the offending field.