Source type
AfterShip Source Configuration
AfterShip sources receive tracking, shipment, and delivery lifecycle webhooks with AfterShip HMAC verification.
AfterShip configuration
Create a AfterShip source, keep POST and PUT and PATCH and DELETE enabled, and provide the configured Webhook Secret values for provider signature. FastHook uses these settings to validate each AfterShip delivery before it enters the routing workflow.
Source TypeAFTERSHIP
Allowed methodsPOST, PUT, PATCH, DELETE
AuthenticationProvider signature
Credential fieldsWebhook Secret
{
"type": "AFTERSHIP",
"config": {
"auth_type": "PROVIDER_SIGNATURE",
"auth": {
"provider": "AFTERSHIP",
"webhook_signing_secret": "provider-secret"
},
"allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
}
}AfterShip request contract
FastHook computes base64 HMAC-SHA256 over the raw body and compares it with aftership-hmac-sha256.
AfterShip headers
Preserve aftership-hmac-sha256 when sending AfterShip test deliveries. FastHook evaluates this request context before accepting the payload, so missing or modified values remain visible as rejected requests instead of routed events.
aftership-hmac-sha256Base64 HMAC-SHA256 signature over the raw body.
AfterShip setup
- Create an AfterShip webhook notification with the FastHook Source URL.
- Paste the webhook secret into FastHook.
- Route by tracking status, carrier, or shipment state.