> ## Documentation Index
> Fetch the complete documentation index at: https://developers.cubbo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Carrier tracking status changed

> Cubbo sends this event to your order webhook URL every time the carrier tracking status of a
shipped order changes (in transit, out for delivery, delivered, incident, returned, canceled,
partially delivered, to be self-collected). A tracking update whose status equals the previous
status is not sent.

- `status` is the shipment status that triggered the event. For multi-package orders it describes
  the package that changed; the full set is listed in `packages`, and `triggered_by_package`
  identifies the one that changed.
- `updated_at` is the timestamp of the carrier event, not the time of delivery of the webhook.
- `incident_description` is set only when `status` is `shipment_with_incident`.
- `estimated_time_arrival` is `null` when the shipment was returned or the package was reported
  stolen or lost.
- `label_tracking_event_id` identifies the exact tracking event; combined with the
  `X-Cubbo-Idempotency-Key` header it lets you deduplicate retries while still receiving one event
  per package.
- `channel_integration_id` and `channel_order_id` are added when the "include channel details in
  webhooks" setting is enabled for your store by Cubbo. `channel_name` and `channel_order_id` are
  included for every recently created Open API integration.
- This event has no `id` field; correlate by `order_number` (unique within a store) or
  `channel_order_id`.




## OpenAPI

````yaml /openapi.yaml webhook shippingUpdated
openapi: 3.1.0
info:
  title: Cubbo Clients API
  version: '1.0'
  summary: >-
    Orders, inventory, replenishments, returns, shipping and webhooks for Cubbo
    fulfillment.
  description: >
    The Cubbo Clients API connects your store, ERP or marketplace with Cubbo's
    fulfillment network.

    All endpoints except `POST /auth/token` require a bearer token; see the
    Authentication guide.

    Request and response bodies are JSON. Errors are JSON objects with an
    `error` key.
  contact:
    name: Cubbo integrations
    email: integraciones@cubbo.com
servers:
  - url: https://api.cubbo.com/v1
    description: Production
security:
  - bearerAuth: []
tags:
  - name: Authentication
    description: Exchange client credentials for a bearer token.
  - name: Orders
    description: Create, update, hold, cancel and read sales orders.
  - name: Shipping labels
    description: Read the shipping labels generated for an order.
  - name: Inventory
    description: Products and stock per store.
  - name: Lots
    description: Lot-level inventory for products with expiration or batch tracking.
  - name: Reports
    description: Bulk reports for reconciliation.
  - name: Replenishments
    description: Inbound shipments to the warehouse.
  - name: Returns
    description: Returns and exchanges.
  - name: Stores
    description: Store provisioning and settings.
  - name: Shipping methods
    description: Available shipping methods, coverage and quotes.
  - name: Click and collect
    description: Pickup points and in-store pickup orders.
paths: {}
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >-
        Token returned by `POST /auth/token`, sent as `Authorization: Bearer
        <token>`.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.