Skip to main content
POST
Book and follow Location

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

Accept-Language
string
default:en

Preferred language(s) for translatable content using BCP 47 language tags. Supports quality values (q-factors) for priority ordering. The API negotiates the best available language based on this header, the team's configured language, and available translations. If omitted, the team's default language is used.

Example:

"da-DK, da;q=0.9, en;q=0.8"

Request-ID
string

Optional client-supplied request identifier. When provided and matching the validation pattern, the value is echoed back in the Request-ID response header. Otherwise the server generates one. Use this to correlate requests between client and server when reporting issues.

Required string length: 1 - 64
Pattern: ^[A-Za-z0-9._-]{1,64}$
Idempotency-Key
string

Optional, case-sensitive key for one intended action. Scope: team, HTTP method and canonical path. Retained for at least 24 hours and while processing. Same key and payload reuses the stored outcome without repeating side effects; the resource representation is current. Changed payload: 422 with an Idempotency-Key entry in errors. Concurrent duplicate: 409 with Retry-After and Location when known. Without a key there is no deduplication. Use GET at Location after 202.

Required string length: 16 - 128
Pattern: ^[A-Za-z0-9._-]{16,128}$

Path Parameters

teamUuid
string<uuid>
required

Team uuid. All resources are scoped to this team.

Body

application/json

Immutable input for one logical booking. Every supplied amount includes value and currency; every supplied weight or dimension includes value and unit. Within one shipment, all non-null amounts use the same currency, all weights use the same unit, and all parcel dimensions use the same unit. Missing or invalid object fields and mixed currencies or units return 422; currency and units never fall back to team defaults. Optional fields may be omitted or null where allowed. No per-booking document/print preference overrides.

delivery
object
required

Selected delivery product and shipment-specific options. A requested delivery window must be supported by that product; an estimate from discovery is not a reservation.

parties
object
required

Omit merchant to use the appropriate team address. Pickup points belong to delivery.

parcels
object[]
required

Parcels in stable input order.

Minimum array length: 1
invoice_number
null | string

Customs invoice number when applicable. Use reference for the public order reference.

Example:

"INV-1001121"

reference
null | string

Public reference, e.g. order number or SKU, which may be forwarded to the carrier or printed. Not necessarily unique.

Example:

"Order-5521"

identifier
null | string

Private integration reference, e.g. a database ID. Not used for deduplication and not forwarded to carrier labels. Not necessarily unique.

Example:

"shop-order-1042"

uri
null | string<uri>

URI linking to the source of this shipment (webshop order URL, deep link, or any URI scheme)

Example:

"https://shop.example.com/admin/orders/1042"

total_net_amount
null | object

Total goods value excluding tax.

Example:
tax_amount
null | object

Total goods tax.

Example:
duty_amount
null | object

Total goods duty.

Example:
shipping_net_amount
null | object

Shipping cost excluding tax.

Example:
shipping_tax_amount
null | object

Shipping tax.

Example:
content_type
enum<string>

Type of contents in the shipment

Available options:
commercial_goods,
returned_goods,
gift,
commercial_sample,
documents,
other

Response

Shipment booked with all required documents and codes ready.

data
object
required

Current immutable booking input plus evolving lifecycle and results. Each shipment has one logical booking. Full event and print histories are retrieved through their own paginated endpoints. A failed document workflow may still have a carrier booking; never blindly rebook such a result. Amounts and measurements include their own currency or unit, preserved from the accepted input. All shipment, parcel and item amounts share one currency; all weights, including dangerous goods, share one unit; all parcel dimensions share one unit. Document dimensions are independent.