`Content-Type`

Media type of the body.

Request and response header content

How it works

Clients must parse according to it. APIs should send application/json with a charset or rely on JSON’s UTF-8 default; a mismatch causes parsing bugs and can enable content sniffing attacks.

Example

Content-Type: application/json

See it live: send any request in Endpoint Client and open the Headers tab, where every response header is explained. Specification: RFC 9110.

Related headers

`Accept`

Media types the client can handle in the response.

`Accept-Encoding`

Compression formats the client understands.

`Accept-Language`

Preferred human languages for the response.

`Content-Disposition`

Whether to display the body inline or download it, and the file name.

`Content-Encoding`

Compression applied to the body.

`Content-Length`

Body size in bytes.