Content type 'application/octet-stream' not supported for bodyType=java.util.Map

[ocean frost]

I'm getting this error when the api returns a response. It works in postman though and I am sending content-type application/json in my request header. Any ideas?

[sick dust]

Hello! I'm AppsmithBot, here to assist you with your Appsmith queries.

To help you with the error you're encountering, could you please provide more details about the error message you're seeing? Additionally, ensure that the API URL, headers, and request body in Appsmith are correctly configured, similar to your Postman setup. You can also check if the API response is being correctly parsed in Appsmith. If you can share the error message or any additional details, that would be helpful!

If you don't find my response helpful, you can request to speak to a human agent.

[ocean frost]

How can I check if the response is being correctly parsed in appsmith?

[Production]
PluginExecutionError:
GET
Api3
:
Content type 'application/octet-stream' not supported for bodyType=java.util.Map<?, ?>

[sick dust]

In Appsmith, you can check if the response is being correctly parsed by following these steps:

1. Inspect the API Response:

• Go to the API pane where you have configured your API.
• Click on the "Test" button to run the API.
• Check the "Response" tab to see the raw response returned by the API.

2. Check the Data Binding:

• Ensure that you are using the correct data binding syntax to access the API response in your widgets. For example, if your API is named Api1, you can access the response data using ** {?{ Api1.data }?} **.

3. Console Logs:

• You can use the console.log function in a JSObject to log the API response and check if it is being parsed correctly. For example:

export default {
logApiResponse: () => {
console.log(Api1.data);
}
}

• Run this function to see the logged response in the browser's console.

4. Error Handling:

• Check if there are any error messages in the "Errors" tab of the API pane, which might indicate issues with parsing.

By following these steps, you should be able to determine if the response is being correctly parsed in Appsmith. If you encounter any specific issues, feel free to share more details!

If you don't find my response helpful, you can request to speak to a human agent.

The error message you're encountering, Content type 'application/octet-stream' not supported for bodyType=java.util.Map, suggests that the API response is being returned as a binary stream (application/octet-stream), which Appsmith is not able to parse as a JSON object.

Here are a few steps you can take to resolve this issue:

1. Check API Configuration:

• Ensure that the API endpoint is supposed to return JSON data. If the API is expected to return a binary file, you might need to handle it differently.

2. Response Type:

• If the API is supposed to return JSON, check if there is an issue with the API itself or if it needs specific headers to return JSON. You might need to set the Accept header to application/json in your API configuration in Appsmith.

3. Inspect the API Response:

• Use Postman or another tool to inspect the API response headers and body to ensure it is returning the expected content type and data.

4. Handle Binary Data:

• If the API is indeed returning binary data and you need to handle it in Appsmith, you might need to adjust your approach to process the binary data accordingly.

If the API is supposed to return JSON and you're still facing issues, you might need to check with the API provider to ensure the endpoint is configured correctly. If you have more details about the API or need further assistance, feel free to share!

If you don't find my response helpful, you can request to speak to a human agent.

[ocean frost]

I use this endpoint other places without issue and I know it returns json. In addition I've tried sending the Accept header with application/json to no avail

[sick dust]

Given that the API works elsewhere and returns JSON, but you're encountering this issue in Appsmith, here are a few additional steps you can try:

1. Double-check Headers:

• Ensure that both Content-Type and Accept headers are set to application/json in your API configuration in Appsmith.

2. Inspect the Raw Response:

• Use the "Test" button in the API pane to inspect the raw response. This can help verify if the response is indeed JSON or if there's an unexpected content type being returned.

3. Check for Transformations:

• Ensure there are no transformations or middleware in Appsmith that might be altering the response content type.

4. Debugging with Logs:

• Use a JSObject to log the response and headers to see if there are any discrepancies:

export default {
logApiResponse: async () => {
const response = await Api3.run();
console.log(response);
}
}

5. Cross-Origin Resource Sharing (CORS):

• Ensure that CORS settings on the server allow requests from your Appsmith instance, as CORS issues can sometimes lead to unexpected behavior.

6. Network Tab in Developer Tools:

• Use the browser's developer tools to inspect the network request and response. This can provide insights into what is being sent and received.

If none of these steps resolve the issue, there might be a specific configuration or environment-related problem. In such cases, it might be helpful to reach out to Appsmith support with detailed logs and configurations.

If you don't find my response helpful, you can request to speak to a human agent.

[ocean frost]

human

[sick dust]

Someone from our team will reach out to you on this thread. In the meantime, you can have a look at our documentation to try & resolve your query https://docs.appsmith.com?utm=bot

[sick dust]

Hello! I'm Amelia with Appsmith Support.
Please share the following information to help us debug this issue:

• What version of Appsmith are you on?
• Provide a screenshot of your API configuration in Appsmith.
• Share a screenshot of the API configuration in another tool where it is working (e.g., Postman or ReqBin).

[ocean frost]

sorry didnt get a notification that you replied. Looking at the sent request, I notice the headers are empty.

obviously not going to show my secret, but its in there

Here is my postman config for the same endpoint

Again, postman works. It looks like the problem in appsmith is that its not sending headers in the request.

[sick dust]

Which version of Appsmith are you on?

[ocean frost]

1.48

This was in the last version as well