Shipping Webhooks

Webhook Payload Structure

When an event occurs, RC:Ship sends a POST request to your configured endpoint. The payload contains the event type, the resource ID, and the data object containing the updated state.

Webhook Payload Example

{
  "id": "evt_0987654321",
  "event": "shipment.delivered",
  "timestamp": "2024-05-20T18:05:00Z",
  "resource": "shipment",
  "resourceId": "shp_a1b2c3d4",
  "data": {
    "status": "delivered",
    "trackingNumber": "AMZ987654321",
    "carrier": "amazon_shipping",
    "location": "Mumbai, MH",
    "description": "Package was handed directly to resident."
  }
}

Supported Events

shipment.created

Fired when a new shipment object is successfully created in RC:Ship.

label.generated

Fired when the carrier successfully returns the manifest and printable label.

shipment.picked_up

Fired when the carrier takes physical possession of the package.

shipment.delivered

Fired when the package reaches its final destination successfully.

shipment.exception

Fired when a delivery exception occurs (e.g., incorrect address, weather delay).

Integrating shipping carriers is notoriously difficult due to archaic SOAP APIs, inconsistent documentation, and varied label formats. RC:Ship abstracts away this complexity, providing a unified developer experience.

Unified Carrier Abstraction

Instead of building and maintaining 10 different carrier integrations, you build one integration to the RC:Ship API. We handle the carrier-specific quirks, API updates, and edge cases, allowing your engineering team to focus on core product features.

Our API normalizes the entire shipping lifecycle—from live rate fetching to label generation and real-time tracking webhooks.

This means that adding a new carrier to your stack is a configuration change in our dashboard, not a three-week sprint for your engineering team.

Reliable Webhooks & Event Streams

Stop polling for tracking updates. Our infrastructure handles millions of carrier pings and distills them into clean, standardized webhook events sent directly to your endpoints. Whether a package is out for delivery or returning to origin, you receive instant, structured JSON payloads.

API Capabilities

RESTful Design

Predictable resource-oriented URLs and HTTP status codes.

Sub-second Responses

Optimized for live checkout rate fetching without latency.

Webhooks

Reliable event delivery with built-in retry mechanisms.

Sandboxed Testing

Generate test labels without incurring real carrier charges.

React to shipping events in real time.

Event Architecture

Webhook Payload Structure

Supported Events

Build with the Shipping Infrastructure API

Unified Carrier Abstraction

Reliable Webhooks & Event Streams

API Capabilities