---
title: "Unsupported Media Type"
description: "The API could not read the request body's encoding. Send uncompressed UTF-8 JSON with the Content-Type header set to application/json."
canonical: "https://signatureapi.com/docs/v1/errors/unsupported-media-type"
source: "https://signatureapi.com/docs/v1/errors/unsupported-media-type.md"
last_verified_api_version: "1.18.0"
last_modified: "2026-11-18T11:41:57Z"
---

# Unsupported Media Type

The API could not read the request body's encoding. Send uncompressed UTF-8 JSON with the Content-Type header set to application/json.

_Last verified against API version 1.18.0._

## What Happened

The API could not read the request body because of how it was encoded. The API returns this error with a `415` status code when:

- The `charset` in the `Content-Type` header is not supported.
- The `Content-Encoding` header names an encoding that is not supported.

> **Tip:** The response includes a `detail` property with more information about this error.

## Example response

```json 415 Unsupported Media Type (application/problem+json)
{
  "type": "https://signatureapi.com/docs/v1/errors/unsupported-media-type",
  "title": "Unsupported Media Type",
  "status": 415,
  "detail": "The request body charset is not supported."
}
```

## How to Fix

- Encode the request body as UTF-8, and set the `Content-Type` header to `application/json` or `application/json; charset=utf-8`.
- Send the request body uncompressed, or remove an unsupported `Content-Encoding` header.

Still stuck? [Contact support](https://signatureapi.com/support).
