Issues with API key authentication

  • 21 July 2021
  • 1 reply

We have an integration with our APP. Users and myself are getting a 401 when testing the authentication. The API keys do work as we have tested them on our end and it works. The customers zaps also work if they are already turned on and active. This is when editing and creating a new one. 



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

1 reply

Userlevel 7
Badge +9

Looks like the request is successfully round-tripping to your server, and the server is just rejecting the credentials - that message came from the API, not the Zapier platform.

The API key auth implementation is really simple. Zapier just takes the string provided and passes it along in the request. A couple thoughts on narrowing down the source of the issue.

  • Have a look at the HTTP logs, both on the Zapier side and on your server side. Is the value mapped to the right param name? Is it included in the right place, header, URL param, etc. 
  • Is there some encoding requirement that the server is expecting?
  • Does the request, with the same API key work in something like Postman? If it does, you’ll want to take a really close look at differences in the two raw http requests.

If none of that works, please share some more detail here and someone will most likely be able to spot the problem.