Skip to main content
Question

How to pass Content-Type in a Custom Request header to avoid errors

  • April 25, 2025
  • 4 replies
  • 81 views

When I pass Content-Type through Header in Custom Request the error I get is 

Failed to create a request in Webhooks by Zapier

The app returned "400".

If I don’t pass the Content-Type my API gets failed as it is not able to reserialize the data sent to a object. 

 

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

4 replies

Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Zapier Orchestrator & Solution Partner
  • 34080 replies
  • April 25, 2025

Hi ​@Datta Shewale 

For us to have more info, post these screenshots:

  • how your Zap step API request is configured in EDIT mode with the field mappings visible
  • the encountered error

 

Also, link to the app API endpoint documentation you used to configure the API request.


JammerS
Forum|alt.badge.img+6
  • Zapier Staff
  • 3527 replies
  • April 28, 2025

Hi ​@Datta Shewale,
 
We just wanted to see how everything is going with your Zap. Did Troy's recommendation get the job done? Feel free to reach out if you need further assistance with your Zap. We're glad to address any concerns and assist you.
 
We're looking forward to your response.


  • Author
  • Beginner
  • 1 reply
  • April 28, 2025

This post has been edited by a moderator to remove personal information. Please remember that this is a public forum and to remove any sensitive information prior to posting.


JammerS
Forum|alt.badge.img+6
  • Zapier Staff
  • 3527 replies
  • April 29, 2025

Hi ​@Datta Shewale,

 

If you're encountering a "400 Bad Request" error in Webhooks by Zapier, it indicates that the server could not process your request due to invalid syntax. To troubleshoot, first, ensure that the Content-Type aligns with your data; for instance, JSON data should have a Content Type of 'application/json.' Next, validate that the data you're sending matches the specified Content and is properly formatted, such as ensuring valid JSON when required. Additionally, check the API documentation for any specific headers or restrictions that might be necessary.

 

We're here to help, so please don't hesitate to reach out if you have any further questions or concerns.