> ## 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.

# Order shipped fulfilled

> Cubbo sends this event to your order webhook URL when the order's shipping labels are generated
and the order leaves packing, i.e. when it becomes `shipped`. It carries the recipient's name and
destination, the carrier, the tracking number of the first package and the Cubbo tracking page URL.
An `orderUpdated` event with `status: shipped` is sent separately for the same transition.

- `tracking_number` is the first package's carrier tracking number; `tracking_urls` contains the
  Cubbo tracking page link, not the carrier's.
- `zip_code` is `"-"` for orders shipped from Chile when no postal code was given; `city` and
  `zip_code` can be `null` for orders the client collects at the warehouse.
- `extended_zone` is added when the "include extended zone in webhooks" setting is enabled for
  your store by Cubbo.
- `order_lines` is added when the "include order line details in webhooks" setting is enabled for
  your store by Cubbo.
- `channel_integration_id`, `channel_order_id` and `subchannel_name` are added when the "include
  channel details in webhooks" setting is enabled for your store by Cubbo.
- `shipping_type`, `delivery_type`, `billing_category` and `latest_estimated_time_arrival_range`
  are added only when those extra fields are enabled for your integration by Cubbo.
- Retries resend the same body. There is no `X-Cubbo-Idempotency-Key` header on this event; use
  `(id, status, updated_at)` or `(order_number, tracking_number)` to deduplicate.




## OpenAPI

````yaml /openapi.yaml webhook orderFulfilled
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.