Hello, I’ve used the REST api to create a rest hook, but getting “Unverified” as it’s status. I’ve also tried to verify it multiple times but no luck. Is there an extra step I need to take? Thanks

How I did it in the past was doing everything in one script. The PHP script runs this statement: $contents = file_get_contents(‘php://input’); If the contents are empty, then it checks and creates the required hook. If the contents were not empty, then it checks if the Hook Secret is present by …

Hello, Thank you for your response. I’ve checked the header that I get back from the call (doing a curl call via php), and there isn’t any ‘X-Hook-Secret’ key-pair in it. Should I do it in another way? Thanks

We pretty much do the same thing only getting/setting the header happens on an isset() instead but same idea.

This works. Thanks a million!! This type of info should be specified in the documentation, here: Keap REST API Where did you get this extra step from? Was I looking in the wrong place?

You had to ask for the documentation when Rest Hooks became available last year. If you want to know more information, drop Michael Fairchild a message at: @MichaelFairchild I noticed that the Developer Documentation has been undergoing recent updates, maybe more information will be added soon.

Rest Hook documentation has been added as well as making the hooks officially live as of ICON. This also includes the addition of hooks for applying and removing tags. We are continuing to add more clarity to the documentation both in general and specific to rest hooks (more info and communication o…

Hey all! So I am also running into this issue, but I am not developing in PHP. Basically right now I am not able to create a webhook either through the interactive rest docs, or through postman. After posting to create the hook, these are the only headers I receive(Status 200): Cache-Control →no…

the x-hook-secret is not passed back to the caller. it is sent to the specified end point where you would need to have code to send the header entry/value back to them to confirm the endpoint is valid. THEN they send back to the caller a response that include the status of that action

Hmmm… okay. I will see if I can figure this out. I am working with workato(similar to zapier) and I don’t have access to the headers, only the payload when it sends the verification call… I assume I could have it send the initial call to something that I can see, verify it, and then update the url…

Or is there a header I can send to have it autoverify?

You’re not going to be able to use that approach. I would use a relay on a server you have access to. Verify/register that as the endpoint. If you want information from that point forward to go anywhere then you have code level access to respond to the data sent from the REST hook.

Unverified REST hook

API Q&A

mike.christianson (Mike Christianson) July 22, 2017, 12:06am 21

See REST Hook Delayed Confirmation Flow: Does it work? - #6 by mike.christianson.

Topic		Replies	Views
Unable to verify REST hook API Q&A	2	799	July 4, 2018
My events are still Unverified - not getting verified using autoverify API Q&A	5	620	March 26, 2019
Rest Hook Verification Trouble API Q&A resthooks	4	949	March 23, 2018
Verifying webhook API Q&A web-hook	2	811	May 21, 2021
REST Hook Delayed Confirmation Flow: Does it work? API Q&A	10	2280	August 8, 2017

Unverified REST hook

Related topics