-
Notifications
You must be signed in to change notification settings - Fork 220
document how to use (and validate) webhooks #195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@zeke Is this info still accurate? Some time in the last few days all the webhooks for my app have stopped working. Need a solution ASAP. |
@platform-kit this should still work. Please email team@replicate.com and share some details about the predictions you ran that have failing webhooks. |
Just did that. Sharing this here too for posterity - Just like the other users report, it's ALL predictions. |
This was solved: https://discord.com/channels/775512803439280149/1203740306722398268 |
Thanks @platform-kit and @Pwntus for following up. 👍🏼 |
Whoops re-opening because we still need to document webhooks here. 😅 |
One thing that caught me by surprise with webhooks is that a 301 error silently fails to deliver. I hadn't realized the route I had provided, If there's a better place to raise this LMK. |
Hey @lukeingalls thanks for reporting. Checking with our webhook provider to see if we can support following redirects. |
@lukeingalls our webhook service doesn't support following redirects, and is not likely to. You will need to use the ultimate destination URL when specifying your webhook.
☝🏼 Yeah that's a great suggestion. I've made a ticket for this internally. |
Hi, I had the same issue between "domain.com/api/..." and "www.domain.com/api/..." for my webhook. |
We should update the README with an example of how to set a webhook.
This page has some prior art: https://replicate.com/docs/webhooks#setting-webhooks
The text was updated successfully, but these errors were encountered: