Send requests
Simple apis to send request with no complicated auth tokens
Enterprise-first webhook infrastructure
We worry about webhooks so that you can focus more your core product
We worry about webhooks so that you can focus more your core product
If you think sending a webhook is as easy as sending an HTTP request, think again
Customer endpoints often fail resulting in breakdown of communication. You need multiple automatic retries, implement circuit breaker, isolate failing endpoints, give you complete logs of the responses received in each try, allow you to setup alerts using custom rules, and many more.
Receivers need to verify the payload isn't modified and coming from the verified static IP address to protect from SSRF, unauthenticated events and replay attacks.
During spikes, the receivers' servers may be overwhelmed and would start rejecting incoming requests but many webhook providers do not smooth out the traffic which leads to data loss.
Webhooks need to deliver information with very low latencies and thus need to be closer to the receivers' servers
For failed deployments, there needs to be a mechanism to replay all the failed events to recover the data loss
Providers need to be cognizant to not send duplicate webhooks to avoid inconsistent state for receiver.
Audits, fine-grained permissions, event types, scalability, fault tolerance are more things to worry about.
Simple apis to send request with no complicated auth tokens