Unsupported media type

Request / unsupported-media-type

The Content-Type specifies a format that this endpoint does not accept.

HTTP 415

How to resolve the problem

1. Check the supported requestBody formats in OpenAPI.
2. For REST endpoints that accept JSON, set Content-Type: application/json.
3. Encode the request body in the format specified by the header.

About this problem type

HTTP 415 means that the submitted format is unsupported. Malformed JSON or a missing required header can still return HTTP 400.

Response example

Response headers

HTTP/1.1 415
Content-Type: application/problem+json
Content-Language: en-US

Example API response

{
    "type": "https://api.szybkisms.pl/problems/unsupported-media-type/",
    "status": 415,
    "title": "Unsupported Media Type",
    "detail": "This endpoint does not support the submitted Content-Type.",
    "code": "415-1",
    "instance": "/rest/messages/sms"
}

code is a diagnostic code for support. instance provides the request path. The example uses the current API identifiers.

Example situations

Filter messages and causesClear1 situations

HTTP 415Whole request failureLink ↗

This endpoint does not support the submitted Content-Type.

Set Content-Type to a requestBody format supported in OpenAPI; use application/json for REST endpoints with JSON bodies.

Any REST endpoint

Problem type identifier

Problem type URI and documentation URL

https://api.szybkisms.pl/problems/unsupported-media-type/

Operation results with HTTP 200

Message sending and statusesQueue acceptance, rejection and subsequent delivery status.

Message pricingPrice calculation results and reasons for unsuccessful pricing.

Cancellation and deletionOperation status and Problem Details for individual failures.