Fedex Advanced Integrated Visibility Webhooks

generated: '2026-11-05'
method: searched
source:
- https://developer.fedex.com/api/en-us/catalog/shipment-visibility-webhook/docs.html
- https://developer.fedex.com/api/en-us/catalog/shipment-visibility-webhook/docs/introduction/monitoring-failures-retry-mechanism.html
- https://developer.fedex.com/api/en-us/catalog/shipment-visibility-webhook/docs/introduction/business-rules-and-best-practices.html
- https://developer.fedex.com/api/en-us/catalog/shipment-visibility-webhook/docs/introduction/test-webhook.html
- https://developer.fedex.com/api/content/dam/fedex-com/irc/documentation/dl_TrackingID_Schema.json
spec_type: Webhooks
name: FedEx Advanced Integrated Visibility (Shipment Visibility Webhook)
description: 'Near real-time tracking push notifications delivered by FedEx to a customer destination URL. Two subscription types: Account Number Subscription (all shipments on registered 9-digit FedEx account numbers) and Tracking Number Subscription (registered tracking numbers). Subscriptions are managed in the Developer Portal and through the Account Number / Tracking Number Subscription APIs (openapi/). Paid product; see plans/fedex-plans-pricing.yml.'
delivery:
  method: HTTPS POST of a JSON payload to the subscription destination URL
  transport_requirements: Only HTTPS connections using TLS (SSL) 1.2 or higher protocol versions that is configured with a certificate from a valid certificate authority (CA) is supported. Destination URL must not be an IP address, localhost or RFC1918 space, and must not use FedEx domain names; 200 character limit.
  acknowledgement: HTTP 200 or 202 from the destination URL; anything else is a failure.
  signature:
    header: fdx-signature
    algorithm: HMAC-SHA256 over the payload keyed with the subscription security token, Base64 encoded
    documented_as: SHA256( security token + payload) = Base 64 encoded fdx-signature as part of payload Header
    security_token: 'Set per subscription: minimum 26 (contract says 25) and maximum 100 characters with at least one uppercase, one lowercase and one numeric character.'
  retries:
    policy: Every event in the case of a failure will be retried 3 times over 15 minutes with 5-minute intervals in between each retry (the retry diagram shows attempts at 1, 2 and 4 minutes +/- jitter).
    missed_events: Failed events are stored for 7 days and can be retrieved by initiating the retry process on the Advanced Integrated Visibility webhook project; missed events are then sent to the subscribed destination URL.
    ordering: Customers must manage the order of the shipment tracking events received on their end. FedEx continues to push new events while retrying an earlier one.
    tier_note: BASIC tier has retry policy upto 6 hours (Account Number Subscription contract).
  response_types:
  - Detailed Tracking Response (entire event history)
  - Event-Specific Tracking Response
payload_schema:
  file: asyncapi/fedex-aiv-webhook-payload-schema.json
  source: https://developer.fedex.com/api/content/dam/fedex-com/irc/documentation/dl_TrackingID_Schema.json
  top_level:
  - scanEvent
  - trackResult
  note: Verbatim JSON schema download offered on the webhook documentation page.
events:
- name: scanEvent
  description: The current tracking milestone of the payload (eventType codes include AE arriving early, AO arriving on time; Picked up, In Transit, Out for Delivery, Delivered, delivery exceptions).
- name: previousEvents
  description: Additional shipment history; some milestones appear only here.
- name: proof of delivery updates
  description: Picture, signature and GPS proof of delivery added after the delivered milestone (wait approximately five minutes after Delivered).
- name: delivery prediction updates
  description: Estimated delivery date and time changes.
management_apis:
- openapi/fedex-account-number-subscription-api-openapi.yml
- openapi/fedex-tracking-number-subscription-api-openapi.yml
testing: Test Webhook URL in the Sandbox Console (see sandbox/fedex-sandbox.yml).
asyncapi_document: null
asyncapi_note: FedEx publishes no AsyncAPI document; this record is read from the webhook documentation.