Documentation
Carrier API (Galaxy)
Carrier API (Galaxy)
  • Carrier [Galaxy]
    • General considerations
      • Resources [api]
        • Metadata [Dictionary]
        • Shipment Modes [Dictionary]
        • Tracking points [Sample]
        • Documents Types [Sample]
        • Content Types [Sample]
        • My accounts
        • *My Active Shippers
      • Postman Project
      • Full Swagger
    • Shipments [webhook]
      • Setting up webhooks
      • Securing webhooks
      • Retry Mechanism
      • Carrier Payloads
    • Trackings [api]
      • By SH ID
        • TPs by SH ID
        • Create TP by SH ID
        • Replan Pickup by SH ID
        • Confirm Pickup by SH ID
        • Replan Delivery by SH ID
        • Confirm Delivery by SH ID
      • By TP ID
        • Update TP location by TP ID
        • Cancel TP by TP ID
        • Replan TP by TP ID
        • Confirm TP by TP ID
    • Metadata [api]
      • Shipment_request scope
        • Get MD by SR ID
        • Create MD by SR ID
        • Update MD by SR ID
      • Shipment scope
        • Get MD by SH ID
        • Create MD by SH ID
        • Update MD by SH ID
    • Documents [api]
      • Shipment scope
        • *Get Attachments by SH_ID
        • Upload Attachment by SH_ID
      • Shipment Request scope
        • *Get Attachments by SR_ID
      • Get Attachment by Attachment ID
Powered by GitBook
On this page
  1. Carrier [Galaxy]
  2. Shipments [webhook]

Retry Mechanism

For Webhook POSTs, Shiptify monitors the response codes from your server and reacts accordingly:

  • If a 200 (Success) code is received, the webhook POST is considered successful, and no further attempts will be made.

  • For any other response code, Shiptify will retry the POST following the schedule below, except for delivery notifications.

  • If your application cannot process the webhook request and does not return a 406 error code, Shiptify will retry for up to 24 hours at the following intervals: immediately, 30 minutes, 1 hour, 4 hours, and 24 hours.

PreviousSecuring webhooksNextCarrier Payloads

Last updated 7 months ago