Webhook Overview

AfterShip Tracking can send webhook events to notify your system when a particular event has happened. Learn to set up webhooks.

You can enable the webhook from the notifications webhooks settings

  • Add webhook URL (up to 4)
  • (Optional) Add custom headers(up to 5 per URL) to the URL for authentication
  • Select events to start receiving updates

We currently support either HTTP or HTTPS URLs, so you can have security by using an SSL-enabled URL. But keep in mind that your endpoint is going to be wide-open on the internet, and you might not want others to be able to submit random data to your systems. At this time, aside from trying to keep the URL private, our best advice is to verify the request using the AfterShip webhook signature or verify the request by the basic authentication, verification (bearer) token, or secret key base on the custom headers.

AfterShip Tracking sends event driven data to webhook URL via POST method. In case of an unsuccessful event (HTTP response code NOT between 200 and 299), AfterShip Tracking attempts to deliver your webhooks for up to 14 times with an exponential back off. The attempts are based on your original webhook setting of the first attempt.

The current attempt webhook delay is calculated by this formula: 2^(number of retry) x 30s

# of attempt# of retryDelay (sec) before send outAcc. Delay (sec)

For example, If the attempt fails, AfterShip Tracking will retry the 2nd attempt 30s later. If the 7th attempts fail, AfterShip Tracking retry the 8th attempt 960s later If the 14th attempts fail, AfterShip Tracking will not send out that webhook any more.