Does this validate the response body?

No. It parses the header token only.

Semantically irrelevant; parsers should treat them as a map.

Content-Type Parser

In the same workflow: API Header Inspector and REST Endpoint Tester.

Content-Type Parser

Paste a Content-Type header value to see type, subtype, and parameters (charset, boundary, etc.).

Content-Type value

Media type

application/json

Type

application

Subtype

json

Charset

utf-8

All parameters

charset

utf-8

Related tools

Request Body Validator — validate JSON body
API Header Inspector — full response headers

Why use Content-Type Parser?

Content-Type strings bundle type, subtype, charset, and multipart boundaries. Split them reliably to debug charset mismatches, missing boundaries on file uploads, and vendor quirks that break strict parsers.

Practical tips

Compare declared charset with actual bytes when text looks mojibake.
Multipart issues often trace to boundary mismatches between headers and body.
Log full Content-Type in API traces—not just application/json.

Common questions

Does this validate the response body?: No. It parses the header token only.
Parameters order?: Semantically irrelevant; parsers should treat them as a map.

About

Parse Content-Type header: type, subtype, charset, boundary, params. Free header parser for API debugging.

Related tools

Used together

Next step

After content-type-parser, continue with API Header Inspector to validate the next API or webhook layer.