How should data validation errors be returned?

  • 8 June 2021
  • 2 replies

Within my API, validation errors are returned with a HTTP error 400 and a message.

When I test the API as an action in Zapier and hit a validation error, zapier flags the zap as failed, emails me to tell me there is an issue but all I get is the first word of the error message as Zapier truncates the message

What happened (You are seeing this because you are an admin):Stack trace:  ResponseError: {"status":400,"headers":{"content-type":"application/json"},"content":"{\"success\":false,\"message\":\"An

How should I be returning validation errors from my API so that Zapier will handle them in a more friendly error. I can’t see any documentation that covers this.

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

2 replies

Userlevel 7
Badge +9

If you’re working in the UI and reviewing the UI docs you might not have seen this section of the CLI docs which are equally applicable when you’re handing errors while developing in the UI.


If that section doesn’t address your question, please share some code snippets around how you’re handling errors today and we can go from there to get you a better answer.

I did see that subsequent to writing the question so my error handling is improved but I still have doubts. 

If the data passed to my API is invalid it returns an error 400. I now catch that, extract the message and code and throw a Zapier error 400. 

Zapier still fails the action but this time it has a nice message.

Is that how validation errors should be handled? 

Is there a way to plugin to the Zapier validation that moans about missing data in the request?