Table of Contents


Kevin Updated by Kevin

Webhooks are a "push" mechanism for communication between two applications. In this case, ShipStream will send an HTTP request with a useful payload of data to a specified URL when a certain event occurs. The receiving application being notified of the event (which can be based on any platform capable of receiving and processing an HTTP request) can then take appropriate action, such as updating data or triggering a process.

Webhooks should be used as an alternative to "polling" whereby your application checks to see if some data has changed, in particular when there is not likely to be any new data since the last update.

Here are some common advantages of using webhooks:

  • Polling is inherently limited in its ability to scale as your business grows because the number and frequency of requests may increase beyond a reasonable limit and exhaust resources on either end. For example, if you poll the same piece of data 100 times before it is updated, webhooks would be 100x more efficient.
  • Webhooks are sent in near-real-time so that your application can be made aware of changes as soon as they happen instead of waiting until the next polling event.
  • Webhooks sometimes include details that are more difficult to obtain with just polling. For example, when a status changes, the webhook payload may include both the old status and the new status.
  • With polling, you can miss intermediate updates. For example, if a shipment progresses from "picking" to "picked" to "packing" and "packed" all before the next time the status is polled, you would not know when the intermediate statuses occurred.

Examples of uses of webhooks commonly include:

  • Trigger some data to be updated in your application using the payload data or data requested from the API.
  • Send an email or post a message to a Slack channel.
  • Log an event for KPIs or anomaly monitoring.
  • Sync data to a third-party system using a no-code or low-code connector like Pipedream, Zapier, or Shopify Flow.

Are webhooks reliable?

When ShipStream sends an HTTP request for a webhook event, the request is only considered a "success" if the receiving application responds with a 200 response code. This ensures that if there was a network issue or your application somehow missed the webhook or was unable to process it, the webhook will be attempted again. ShipStream will make many attempts to retry the webhook so if there is any temporary outage of your application, there will be no data loss as all failed webhooks will be retried automatically.

Webhook events are recorded in ShipStream's transactional database so that if an event occurs that warrants a webhook, there will absolutely be a corresponding webhook event for it. Combined with the retry mechanism and assuming your application doesn't return a 200 response code incorrectly, there should be no way that a webhook is ever missed unless your application is down for several consecutive days.

Error Handling

In the case of a timeout or other connection error or a non-200 response, the webhook will be retried up to 14 times using the following schedule, advancing the next retry time for each consecutive failure:

  • +1 minute
  • +2 minutes
  • +4 minutes
  • +8 minutes
  • +15 minutes
  • +30 minutes
  • +1 hour
  • +2 hours
  • +4 hours
  • +8 hours
  • +16 hours
  • +24 hours
  • +24 hours
  • +24 hours

Additionally, when a webhook fails on the first attempt, this is logged as an Integration Error and a notice will be displayed on the Client UI panel if there are any unresolved errors.

If the webhook succeeds on a retry, the error is automatically marked as Resolved so the alert automatically disappears when there are no unresolved errors.

The error details can be seen in the Admin UI or Client UI under System > Integration > Errors. Like most other errors, they can be manually marked as Resolved, meaning the system will not retry them anymore and the dashboard notice is no longer applicable.

It is recommended to mark errors that no longer need to be addressed in some way as Resolved to dismiss them from your dashboard notice and separate them from new errors to improve the visibility of urgent issues.

You can also click Retry to force an immediate attempt which can be helpful when troubleshooting.


Notifications are sent to the Technical Contact every 2 hours for all webhooks that are in an error state. When a webhook is successful the error status is cleared automatically.

Throttling and Deactivation

When a webhook is experiencing ongoing issues for over an hour it will be "throttled" causing the number of attempts to decrease until a successful response is received. This reduces unnecessary resource waste and prevents flooding your webhook endpoint as failing requests pile up in the event of an availability incident. The throttling is automatically returned to normal when the endpoint starts responding with a success status again.

If your webhook continues to fail for one week, it will be automatically deactivated and a notification will be sent to the Technical Contact. It can be reactivated manually but will not be reactivated automatically.

Creating a Webhook

Webhooks are often created programatically via the API when an application connects successfully, but can also be created by users on an as-needed basis.

  1. Navigate to System > Integrations > Webhooks
  2. Click Add New Webhook
  3. Fill the form and click Save
Admin UI users have the option of creating a Global webhook which will apply to events generated on behalf of all merchants. Client UI users can only create and view webhooks which apply to themselves.
The webhook Topics and their corresponding POST request payloads are described here.


For data security reasons, ShipStream requires that the receiving endpoint implement the HTTPS protocol with a valid and non-expired SSL certificate to prevent any eavesdropping. This ensures that the payload is strongly encrypted as it is being transmitted.

Additionally, it is wise to validate that the webhook payload is authentic should the location of your endpoint or the details of your implementation become known to a malicious actor. Payload validation using an HMAC signature is the best method to protect your endpoint, but this is not enforced by ShipStream so it is up to you to implement some validation. HMAC signature validation is covered below with examples for common programming languages.


Webhook authenticity can be verified by the X-Plugin-Hmac-Sha256 HTTP header which is included with every webhook request. You can compare this header value with the HMAC generated locally to ensure that the request was not spoofed or modified in transit. The HMAC “message” is the entire request body and the HMAC “secret” is the "Secret Key" associated with the webhook when it was created.

PHP Example

// Define your webhook secret key
$webhookSecretKey = 'your-webhook-secret-key';

// If the header is not present, respond with 401 Unauthorized
$headerValue = $_SERVER['HTTP_X_PLUGIN_HMAC_SHA256'] ?? '';
if (!$headerValue) {

$json = file_get_contents('php://input');
$expectedValue = base64_encode(hash_hmac('sha256', $json, $webhookSecretKey, TRUE));
if ($headerValue !== $expectedValue) {

// Handle the webhook request here

Node JS Example

const express = require('express');
const crypto = require('crypto');
const bodyParser = require('body-parser');

const app = express();

// Define your webhook secret key
const webhookSecretKey = 'your-webhook-secret-key';

// body-parser is the first Express middleware.
app.use(bodyParser.json({ verify: function(req, res, buf, encoding) {
const headerValue = req.headers['x-plugin-hmac-sha256'];
const expectedValue = crypto
.createHmac('sha256', webhookSecretKey)
if (headerValue !== expectedValue) {
throw new Error("Invalid signature.");
} else {
console.log("Valid signature!");

// Route for handling webhook requests'/webhook', (req, res) => {
// Handle the webhook request here

// Start the server
app.listen(3000, () => {
console.log('Server is running on port 3000');

Python Example

from flask import Flask, request
import hmac
import hashlib

app = Flask(__name__)

# Define your webhook secret key
webhook_secret_key = b'your-webhook-secret-key'

# Middleware to validate the contents of the request
def validate_request():
header_value = request.headers.get('X-Plugin-Hmac-Sha256')

# If the header is not present, respond with 401 Unauthorized
if not header_value:
return 'Unauthorized', 401

data =
expected_value =, data, hashlib.sha256).digest()
expected_value = expected_value.encode('base64').strip()
if header_value != expected_value:
return 'Unauthorized', 401

# Route for handling webhook requests
@app.route('/webhook', methods=['POST'])
def handle_webhook():
# Handle the webhook request here
return 'OK', 200

# Start the server
if __name__ == '__main__':

ASP.NET Core Example

using System;
using System.IO;
using System.Security.Cryptography;
using System.Text;
using Microsoft.AspNetCore.Builder;
using Microsoft.AspNetCore.Hosting;
using Microsoft.AspNetCore.Http;
using Microsoft.Extensions.DependencyInjection;

public class Startup
// Define your webhook secret key
private byte[] webhookSecretKey = Encoding.UTF8.GetBytes("your-webhook-secret-key");

public void ConfigureServices(IServiceCollection services)

public void Configure(IApplicationBuilder app, IHostingEnvironment env)
app.Use(async (context, next) =>
string headerValue = context.Request.Headers["X-Plugin-Hmac-Sha256"];

// If the header is not present, respond with 401 Unauthorized
if (string.IsNullOrEmpty(headerValue))
context.Response.StatusCode = 401;

using (var reader = new StreamReader(context.Request.Body))
string data = await reader.ReadToEndAsync();
byte[] expectedValue = new HMACSHA256(webhookSecretKey).ComputeHash(Encoding.UTF8.GetBytes(data));
string expectedValueBase64 = Convert.ToBase64String(expectedValue);

if (headerValue != expectedValueBase64)
context.Response.StatusCode = 401;

await next.Invoke();

app.UseMvc(routes =>
name: "default",
template: "{controller=Home}/{action=Index}/{id?}");

How did we do?

ShipStream Plugin Fostering Program