What are EasyPost Webhooks? And how do they work?
How do I secure my Webhooks?
How can I retry failed events on your tracking webhooks?
Do I need multiple endpoints when setting up tracking webhooks?
How are webhook requests delegated when I have multiple endpoints set up?
What are EasyPost Webhooks? And how do they work?
EasyPost Webhooks are callbacks that provide an Event update via HTTP POST to each configured webhook URL.
In order to take advantage of webhooks, all you need to do is add your webhook URLs to your account page. The way these webhook events are processed will be specific to your application.
For more information about how our webhooks work, take a look at our webhook documentation.
How do I secure my Webhooks?
For now, our recommendation for securing webhooks involves using basic authentication and HTTPS on your endpoint. This helps prevent any altering of any information communicated to you by EasyPost, and it will prevent any third parties from masquerading as EasyPost in order to send you fraudulent data.
Here is an example of how you could add basic authentication to your webhook URL:
https://username:secret@www.example.com/webhook
How can I retry failed events on your tracking webhooks?
We'll automatically retry failed attempts on your webhook, but currently there is not a way to retry failed events manually.
Do I need multiple endpoints when setting up tracking webhooks?
For most people, we would recommend only using one endpoint for your webhooks. The only benefit to using multiple endpoints if your system set up requires you to have multiple - e.g. if you have multiple siloed systems that want to receive webhook requests. There is no performance boost to using multiple endpoints for a single system.
How are webhook requests delegated when I have multiple endpoints set up?
Each pending webhook requests to all of your registered webhook URLs. As of right now, we don't support the ability to specify a specific webhook endpoint any given object sends update requests to.
Comments
0 comments
Article is closed for comments.