HTTP 415 Unsupported Media Type Error

Main causes

The `Content-Type` header in the request is a format not supported by the server.
The `Content-Encoding` header specifies an encoding that the server is unable to process.
The server is unable to handle or recognize the data structure of the payload after inspecting it.
The request is targeting an endpoint that specifically requires a different content format than what is provided.

# Request example 
curl -X GET https://sandbox.oxylabs.io/ -H 'Accept: application/xhtml+xml' -H 'Accept-Encoding: br' -H 'User-Agent: Safari/537.36'

Ensure the Content-Type header in your HTTP request matches the format the server is capable of processing.
Verify that the payload format is supported by the server by checking the server's documentation or configuration.
Convert your data into a compatible format before sending it to the server.
Add or update the Accept header in your request to match the media types supported by the server.

# Response example 
HTTP/1.1 415 Unsupported Media Type
Content-Type: text/plain; charset=utf-8
Content-Length: 35

Unsupported media type requested.

Web scraper API

Self-Service

Public data delivery from a majority of websites

From

401 Unauthorized	403 Forbidden	404 Not found	405 Method not allowed	406 Not acceptable
407 Proxy authentication required	408 Request timeout	409 Conflict	410 Gone	411 Length required
412 Precondition failed	413 Payload too large	414 Uri too long	415 Unsupported media type	416 Range not satisfiable
417 Expectation failed	421 Misdirected request	422 Unprocessable entity	423 Locked	424 Failed dependency
426 Upgrade required	428 Precondition required	429 Too many requests	431 Request header fields too large	444 Connection: close
451 Unavailable for legal reasons	499 Client closed request	501 Not implemented	503 Service unavailable	505 Http version not supported
506 Variant also negotiates	507 Insufficient storage	508 Loop detected	510 Not extended	511 Network authentication required