Asking because I don’t know, well have tried something but get a 504 error (timeout) so am clearly needing to learn more…
Need to be able to demonstrate to someone the web hook works from outside. It does from your test button but not from their API
\edit
just check my OttoReceiver file and that data is there, the 504 error is something else at play.
Have you tried adding the API key as a header instead of a query parameter? Not sure if we’ve updated the docs for this everywhere, but you can use this header
Authorization: Bearer dk_yourkeyhere
Otherwise you may need to post more detail about what you’re seeing
I was just trying to find an easy external way of testing the web hook, from outside so I could pass that information to a jot forms support request where the form wasn’t triggering the web hook on submit.
I had done that and used Postman to do a post to that url with a simple JSON body, but got a 504 timeout error, when I checked later the payload had arrived in my OttoReceiver file - so in fact I had tested it
The built in test works exactly as expected.
The issue is, just as saying ‘well it works here for a customer service call’, troubleshooting list is
Does it work internally
Does it work externally
Does it work from the service I have hooked the webhook to
I am just not sure I am following. Here is what I think you are saying.
The web hook works from the Test button. (This just makes a post from the browser. Should be very similar to Postman)
It does NOT work when you try to do it from Postman.
If that is the case I would like to know more because it should work from Postman. If it doesn’t then we need to track down why. Is there anything else you can tell us that might help us recreate the issue?
It does work from Postman - and by that I mean the payload and channel end up as a new record in my receiver file - but Postman got a 504 error which initially made me think it had not worked…
Hmmm Postman should not get a 504. It should get a 200. Webhooks must return a 2xx level response to the caller otherwise the caller may call again. So If that is what it is happening I would like to try to recreate it. So far I have been unable to. I always get something like this.