Summary of HTTP Request
- How to fix 415 error?
- What is a 415 error?
- What does the 415 code mean?
- What is the reason code 415?
Search Results
AI Overview
AI Overview
A
415 Error is an HTTP status code that means “Unsupported Media Type”. The server refuses to accept the request because the format of the data (the “payload”) being sent is in a format not supported by the server for the given operation.
Common Causes
The error typically results from a mismatch between what the client sends and what the server is configured to accept. Common causes include:
Incorrect Content-Type header: The most frequent cause is when the Content-Type header in the request does not match the actual data format being sent. For example, sending JSON data but specifying text/plain as the content type.
Unsupported media type: The server’s configuration does not support the specific media type (MIME type) indicated in the request header. For instance, an API might only accept application/json but the client sends application/xml.
Incorrect Content-Encoding header: The data is compressed or encoded in a way the server does not understand or is not configured to decode (e.g., using gzip without the server having the necessary module enabled).
Typos or non-standard naming: Simple errors like using charset=UTF8 instead of the standard charset=UTF-8 can cause the server to reject the request.
How to Fix a 415 Error
Fixing the error involves ensuring the client and server agree on the data format and encoding.
Verify the Content-Type header: Double-check that the Content-Type header in your request is present and correctly specifies the format of the data you are sending (e.g., application/json for JSON data).
Check the server’s accepted types: Consult the API documentation or use tools like browser developer tools (in the Network tab) to see what media types the server actually expects or is willing to process. The Accept header in the server’s response can provide hints on the expected input format.
Ensure correct encoding: If you are using compression, ensure the Content-Encoding header is correct and that the server is configured to handle that specific encoding format.
Correct client-side configuration: If using a client-side tool or library (like Postman or a specific programming library), make sure it is configured to send the correct headers and data format. For example, in Postman, ensure you select “JSON” from the dropdown menu for the body type instead of the default “Text”.
Update server configuration: If you control the server, you may need to update its configuration files (e.g., in Apache or Nginx) to support the required media type or encoding.
415 Unsupported Media Type – KeyCDN Support
May 5, 2023 — 415 Unsupported Media Type. … As a website owner or developer, you know how frustrating it can be when your website doesn’t func…
KeyCDN
Resolving the HTTP 415 Error on Your Website – 10Web
Mar 1, 2024 — Resolving the HTTP 415 Error on Your Website * What is the HTTP 415 error? * Variations of this error. * Reasons why this error oc…
10Web
What Is a 415 Status Code? Causes, Fixes, and Best Practices
Jul 7, 2025 — Key Takeaways * The 415 status code indicates that the server can’t handle the format due to a wrong or missing header. * Always v…
IPRoyal.com
Show more
(Mc)
1
Hi. I’m currently trying to request the following API, here’s how it looks like in Postman:
It’s supposed to respond with a “requestSent”: true, but it keeps on returning a 415 Error, kindly check last pic
And here’s how the request looks in the HTTP request wizard (UiPath Activity)
And this is the error I get:
Are my parameters modified incorrectly, how can I make this work?
Thanks,
Mc
Simple enough question, however, have you placed your parameter values in quotations in UiPath
(Troy)
3
Hi @UiP_Mc,
Instead of putting in your json variables as parameters, take the json exactly as you see in postman and put in the body of the request. See if that works.
Cheers.
Troy
(Mc)
5
How do I do this? There’s no body to input the request payload. Just a ‘add a parameter’ button
(Troy)
6
@UiP_Mc,
Once you close the wizard and look at the HttpClient properties, you’ll see Body under options. Put your payload here. I don’t see that option in the wizard.
1 Like
(Mc)
7
Hey @tmays, I tried this, but I don’t know how to debug this error:
I just copied and pasted the exact request body from postman to the properties.
Thanks,
Mc
(Mc)
8
Hi @ronanpeter, I tried to put double quotations but it prompted a different error, I don’t think quotations are needed when supplying the value of the parameters.
I also tried to add the parameters one by one in the properties editor and this is what I get as a response:
I tried looking it up, and it said that it might be because of an unsupported format.
Here’s my Body Format:
(Troy)
9
Hey @UiP_Mc. I think your BodyFormat is fine as application/json and @ronanpeter is correct about the double quotes (in places).
For the key value pair, the key is not quoted and the value, if string, requires a double quote. The start of your body should look like this:
” {
requesterName : ““engineer bob””,
phoneNumber: “”+639985782272″“,
…
}”
The beginning single quote starts the string, no quotes around the key of the key/value pair (because they’re already included as part of the overall string), and double quotes around the value of the key/value pair. Those will be changed to single quotes when processed.
Let me know how this works out.
Cheers!
Troy
(Mc)
10
Hi. I found a solution to this from a similar case:
So the Body(String) shouldn’t have a single space, and everything should be double quoted e.g. “”“requisitionNumber”“:”“123″”,““requisitionDescription””:““sample Description”””
Thanks Troy,
Mc
(Troy)
11
So the double quotes around the key worked?
(Mc)
12
Yup. It has to be enclosed like a string
(system)
Closed
14
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.