GROperator

Shipments

A shipment is created through the same engine as the dashboard: coverage check, monthly quota, rate-card pricing, estimated delivery date, tracking number, and the shipment.created webhook event are all identical. This guide explains how to create shipments for a merchant or a one-off sender, how returns and exchanges work, how a shipment moves through its statuses, and how to track, print, update and cancel it.

Scopes: shipments:write to create, update and cancel; shipments:read to list, get, track and print. Writing does not include reading. For a password login the dashboard permission is checked exactly: orders:create to create, orders:update to update, orders:cancel to cancel. An API key needs only the scope.

Numbers have upper bounds (for example weight at most 9,999,999 kg and each dimension at most 100,000 cm); larger values answer 400 validation_failed. See Conventions.

POST /shipments returns 201 with the full shipment. The shipping fee is never sent: it is computed from your company's rate card. To show the fee before ordering, use a price quote.

sender.type = "merchant" books the shipment for one of your merchants. sender.merchant is the merchant id or the exact account name (case and Arabic letter variants are ignored). A name shared by two merchants answers 422 merchant.ambiguous with details.candidates: use the id. When pickup is omitted, the merchant's primary saved address is the pickup.

POST /shipments
curl -X POST "https://api.goldrock.live/api/public/v1/shipments" \
  -H "X-API-Key: lmc_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
  -H "X-API-Secret: YOUR_API_SECRET" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: order-1001" \
  -d '{
  "reference": "ORD-1001",
  "serviceType": "delivery",
  "serviceTier": "standard",
  "sender": {
    "type": "merchant",
    "merchant": "Noor Electronics"
  },
  "recipient": {
    "country": "SA",
    "city": "Riyadh",
    "district": "Al Olaya",
    "addressLine": "King Fahd Road, Building 12, Floor 3",
    "shortAddress": "RNBA6769",
    "name": "Khaled Alotaibi",
    "phone": "0555123456"
  },
  "parcel": {
    "weightKg": 1.5,
    "lengthCm": 20,
    "widthCm": 15,
    "heightCm": 10,
    "pieces": 1,
    "description": "Mobile phone case",
    "declaredValue": 250,
    "fragile": false
  },
  "payment": {
    "codAmount": 199.5,
    "freightOnDelivery": false
  },
  "delivery": {
    "allowOpenPackage": false,
    "requireSignature": true
  }
}'
JSON
{
  "trackingNumber": "AWB-RUH-000123",
  "reference": "ORD-1001",
  "status": "created",
  "statusCode": 1020,
  "statusLabelAr": "تم إنشاء الطلب",
  "statusLabelEn": "Order Created",
  "isFinal": false,
  "serviceType": "delivery",
  "serviceTier": "standard",
  "source": "api",
  "createdAt": "2026-01-15T09:30:00Z",
  "estimatedDeliveryDate": "2026-01-17",
  "sender": {
    "type": "merchant",
    "name": "Noor Electronics",
    "phone": "0501234567",
    "email": "orders@noor-electronics.example",
    "merchant": {
      "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
      "name": "Noor Electronics"
    }
  },
  "pickup": {
    "country": {
      "id": "5a6f7c1c-1a3e-4c1f-9d5c-3f0d7d2a1b01",
      "nameAr": "المملكة العربية السعودية",
      "nameEn": "Saudi Arabia"
    },
    "city": {
      "id": "f1e2d3c4-b5a6-4978-8a9b-0c1d2e3f4a5b",
      "nameAr": "الرياض",
      "nameEn": "Riyadh"
    },
    "district": {
      "id": "c2d3e4f5-0a1b-4c2d-8e3f-4a5b6c7d8e91",
      "nameAr": "العليا",
      "nameEn": "Al Olaya"
    },
    "addressLine": "King Fahd Road, Warehouse 4",
    "shortAddress": "RNBA6769",
    "latitude": null,
    "longitude": null
  },
  "recipient": {
    "name": "Khaled Alotaibi",
    "phone": "0555123456",
    "secondaryPhone": null,
    "country": {
      "id": "5a6f7c1c-1a3e-4c1f-9d5c-3f0d7d2a1b01",
      "nameAr": "المملكة العربية السعودية",
      "nameEn": "Saudi Arabia"
    },
    "city": {
      "id": "f1e2d3c4-b5a6-4978-8a9b-0c1d2e3f4a5b",
      "nameAr": "الرياض",
      "nameEn": "Riyadh"
    },
    "district": {
      "id": "c2d3e4f5-0a1b-4c2d-8e3f-4a5b6c7d8e91",
      "nameAr": "العليا",
      "nameEn": "Al Olaya"
    },
    "addressLine": "King Fahd Road, Building 12, Floor 3",
    "shortAddress": "RNBA6769",
    "latitude": null,
    "longitude": null
  },
  "parcel": {
    "weightKg": 1.5,
    "lengthCm": 20,
    "widthCm": 15,
    "heightCm": 10,
    "chargeableWeightKg": 1.5,
    "pieces": 1,
    "description": "Mobile phone case",
    "declaredValue": 250,
    "fragile": false,
    "requiresColdChain": false,
    "coldChainRange": null,
    "flammable": false,
    "hazardous": false,
    "containsAlcohol": false,
    "liquid": false,
    "highValue": false
  },
  "delivery": {
    "allowOpenPackage": false,
    "requireSignature": true,
    "requireIdVerification": false,
    "allowNeighborDelivery": true
  },
  "payment": {
    "codAmount": 199.5,
    "shippingFee": 30,
    "freightOnDelivery": false
  },
  "pieces": [
    {
      "barcode": "AWB-RUH-000123-P1"
    }
  ],
  "branch": {
    "id": "8d3c7f52-4b1e-4a90-b6d2-1e5f9a0c3b74",
    "name": "Riyadh Hub"
  },
  "canCancel": true,
  "isEditable": true
}

sender.type = "custom" is for a person or business that is not one of your merchants, for example a customer of your website who ships a parcel. It needs sender.name, sender.phone and a pickup address. The shipment is booked on the company's shared walk-in account. Places here use Arabic names: the spelling variants are handled for you (Places by name).

POST /shipments
curl -X POST "https://api.goldrock.live/api/public/v1/shipments" \
  -H "X-API-Key: lmc_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
  -H "X-API-Secret: YOUR_API_SECRET" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: web-order-58213" \
  -d '{
  "reference": "WEB-58213",
  "serviceTier": "express",
  "sender": {
    "type": "custom",
    "name": "Sara Ahmed",
    "phone": "0501234567",
    "email": "sara@example.com"
  },
  "pickup": {
    "country": "SA",
    "city": "الرياض",
    "district": "حي العليا",
    "addressLine": "طريق الملك فهد، مبنى 12",
    "shortAddress": "RNBA6769",
    "latitude": 24.7136,
    "longitude": 46.6753
  },
  "recipient": {
    "country": "SA",
    "city": "جده",
    "district": "حي البرية",
    "addressLine": "شارع الأمير سلطان، عمارة 4",
    "shortAddress": "JEDA2345",
    "name": "خالد العتيبي",
    "phone": "0555123456",
    "secondaryPhone": "0555987654"
  },
  "parcel": {
    "weightKg": 3,
    "lengthCm": 40,
    "widthCm": 30,
    "heightCm": 20,
    "description": "Clothes",
    "declaredValue": 600
  },
  "payment": {
    "codAmount": 0,
    "freightOnDelivery": true
  }
}'

Required fields are marked. Everything else is optional.

Field Details
reference Your own order reference, up to 100 characters. Printed on the label and searchable
serviceType delivery (default), exchange or return
serviceTier standard (default), express or sameDay. It drives the estimated delivery date
sender Required for key and staff credentials. type is merchant or custom. A merchant login always sends as its own merchant and cannot use custom (403)
sender.merchant Required for type: merchant: id or exact name
sender.name, sender.phone Required for type: custom. sender.email is optional
pickup Where the courier collects. Optional for a merchant sender (the primary address is used), required for a custom sender and for a return
pickup.country Optional when the city name is unambiguous
pickup.city, pickup.district Required when pickup is sent. Id, code or name
pickup.addressLine Required, up to 500 characters: street, building, landmark
pickup.shortAddress Saudi national short address, 4 letters then 4 digits. Required for pickups in Saudi Arabia
pickup.latitude, pickup.longitude Optional, -90 to 90 and -180 to 180
pickup.branch Optional branch id, code or name. By default the branch covering the pickup district is chosen automatically; if none or several cover it you must name one (branch_coverage.no_coverage_for_city, branch_coverage.ambiguous_coverage)
recipient Required except for returns. Same address fields as pickup, all of them required in the same way
recipient.name Required, up to 200 characters
recipient.phone Required, up to 30 characters: digits, spaces, +, - and brackets
recipient.secondaryPhone Optional second phone, same format
parcel.weightKg Required, greater than 0. The weight of the whole shipment
parcel.lengthCm, widthCm, heightCm Required, greater than 0. Dimensions of the whole shipment
parcel.pieces 1 to 1000, default 1
parcel.description What is inside, up to 500 characters, shown on the label
parcel.declaredValue Value of the goods, 0 or more, default 0
parcel.fragile, flammable, hazardous, containsAlcohol, liquid, highValue Handling flags, default false. They can add handling surcharges
parcel.requiresColdChain Default false. When true, parcel.coldChainRange is required: frozen, chilled or ambient
payment.codAmount Cash to collect from the recipient, 0 or more, default 0. Must be 0 for a return
payment.freightOnDelivery true when the recipient pays the shipping fee at the door. Default false
delivery.allowOpenPackage The recipient may open the parcel before accepting. Default false
delivery.requireSignature A signature is required. Default true
delivery.requireIdVerification The courier checks the recipient's ID. Default false
delivery.allowNeighborDelivery A neighbour may accept the parcel. Default true

parcel.chargeableWeightKg in the response is the larger of the actual and the volumetric weight; it is the weight your price is based on.

A return collects a parcel from a customer and sends it back to the merchant. Use serviceType: "return" with a merchant sender. pickup is the customer's address (the place the courier collects from) and is required. There is no recipient: the parcel goes to the merchant's primary saved address, and the receiver details are taken from it. A return cannot carry a COD amount (payment.codAmount must be 0).

POST /shipments
curl -X POST "https://api.goldrock.live/api/public/v1/shipments" \
  -H "X-API-Key: lmc_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
  -H "X-API-Secret: YOUR_API_SECRET" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: return-ORD-1001" \
  -d '{
  "reference": "RET-1001",
  "serviceType": "return",
  "sender": {
    "type": "merchant",
    "merchant": "Noor Electronics"
  },
  "pickup": {
    "country": "SA",
    "city": "Riyadh",
    "district": "Al Olaya",
    "addressLine": "King Fahd Road, Building 12, Floor 3",
    "shortAddress": "RNBA6769"
  },
  "parcel": {
    "weightKg": 1.5,
    "lengthCm": 20,
    "widthCm": 15,
    "heightCm": 10,
    "description": "Returned phone case"
  }
}'

An exchange (serviceType: "exchange") delivers a replacement item to the recipient and comes with a linked return shipment for the item coming back. You create it like a normal delivery, with a recipient. Cancelling the exchange also cancels its pending return, and the service type of an exchange cannot be changed once its linked return exists.

POST /shipments
curl -X POST "https://api.goldrock.live/api/public/v1/shipments" \
  -H "X-API-Key: lmc_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
  -H "X-API-Secret: YOUR_API_SECRET" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: exchange-ORD-1001" \
  -d '{
  "reference": "EXC-1001",
  "serviceType": "exchange",
  "sender": {
    "type": "merchant",
    "merchant": "Noor Electronics"
  },
  "recipient": {
    "country": "SA",
    "city": "Riyadh",
    "district": "Al Olaya",
    "addressLine": "King Fahd Road, Building 12, Floor 3",
    "shortAddress": "RNBA6769",
    "name": "Khaled Alotaibi",
    "phone": "0555123456"
  },
  "parcel": {
    "weightKg": 1.5,
    "lengthCm": 20,
    "widthCm": 15,
    "heightCm": 10,
    "description": "Replacement phone case"
  }
}'

Send an Idempotency-Key on every create, derived from your own order (for example order-1001). If a response is lost, send the same request again: the first answer is returned with Idempotent-Replayed: true and no second shipment is created. See Conventions.

A body that breaks a rule is rejected with 400 validation_failed, and details.errors maps every failing field path to its messages, so you can show all problems at once:

JSON
{
  "code": "validation_failed",
  "message": "One or more fields are invalid.",
  "status": 400,
  "details": {
    "errors": {
      "recipient.phone": [
        "Recipient phone is required."
      ],
      "parcel.weightKg": [
        "Weight must be greater than 0."
      ],
      "recipient.shortAddress": [
        "Short address must be 4 letters followed by 4 digits, for example RNBA6769."
      ]
    },
    "messageAr": "بعض الحقول غير صالحة."
  },
  "traceId": "00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01"
}

Saudi addresses need the short address. Here the pickup was in Saudi Arabia and the merchant sent none:

JSON
{
  "code": "validation_failed",
  "message": "One or more fields are invalid.",
  "status": 400,
  "details": {
    "errors": {
      "pickup.shortAddress": [
        "Short address is required for a pickup in Saudi Arabia (e.g. RNBA6769)."
      ]
    },
    "messageAr": "بعض الحقول غير صالحة."
  },
  "traceId": "00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01"
}

Every shipment has a status key (a string such as outForDelivery), its numeric statusCode, labels in both languages and an isFinal flag. The catalogue is the same for everyone and is served by GET /shipments/statuses; fetch it once and cache it. Use the key in your own code.

The stages and the usual path:

Text
Pickup        created → pickupScheduled → outForPickup → pickedUp
Linehaul      arrivedAtOriginHub → inTransit → arrivedAtDestinationHub → sortedToShelf
Warehouse     onHoldWarehouse → (holdExpiredPendingAction)
Delivery      assignedToCourier → outForDelivery → delivered
                                   ↘ deliveryAttempted / postponedByCustomer / withCourier
                                     (a new attempt returns to outForDelivery)
Exceptions    rtoInitiated → rtoInTransit → returnedToSender
              cancelled, lost, damaged, disposed, partiallyDelivered

A shipment does not have to touch every status, and the numeric codes group the stages rather than guarantee an order. Final statuses never change again: delivered, returnedToSender, cancelled, lost, disposed.

StageCodeKey (status)NameFinal
Pickup1010draftDraft
مسودة
Pickup1020createdOrder Created
تم إنشاء الطلب
Pickup1030pickupScheduledPickup Scheduled
مجدول للاستلام
Pickup1040outForPickupOut For Pickup
خرج للاستلام
Pickup1050pickedUpPicked Up
تم الاستلام
Sorting and linehaul2010arrivedAtOriginHubArrived at Origin Hub
وصل مركز الفرز الأول
Sorting and linehaul2020inTransitIn Transit
جاري النقل بين المدن
Sorting and linehaul2030arrivedAtDestinationHubArrived at Destination Hub
وصل مركز التوزيع النهائي
Sorting and linehaul2040sortedToShelfSorted to Shelf
مفروز على الرف
Warehouse hold3010onHoldWarehouseOn Hold in Warehouse
مخزن بالمستودع
Warehouse hold3020holdExpiredPendingActionHold Expired - Action Needed
انتهت مهلة التخزين
Last mile delivery4005assignedToCourierAssigned to Courier
مسندة للمندوب
Last mile delivery4010outForDeliveryOut For Delivery
خرج للتوصيل
Last mile delivery4020deliveryAttemptedDelivery Attempted
محاولة توصيل فاشلة
Last mile delivery4030postponedByCustomerPostponed by Customer
مؤجل بطلب العميل
Last mile delivery4040deliveredDelivered
تم التسليم بنجاح
yes
Last mile delivery4050partiallyDeliveredPartially Delivered
تسليم جزئي
Last mile delivery4060withCourierWith courier (failed attempt)
بعهدة المندوب (تعذّر التوصيل)
Returns and exceptions5010rtoInitiatedRTO Initiated
بدء الإرجاع للمرسل
Returns and exceptions5020rtoInTransitRTO In Transit
المرتجع في الطريق
Returns and exceptions5030returnedToSenderReturned to Sender
تم الإرجاع للمرسل
yes
Returns and exceptions5040cancelledCancelled
ملغاة
yes
Returns and exceptions5050lostLost
مفقودة
yes
Returns and exceptions5060damagedDamaged
تالفة
Returns and exceptions5070disposedDisposed
تم الإتلاف
yes

Two flags on the shipment save you from guessing: canCancel (the shipment can still be cancelled) and isEditable (it can still be edited).

GET /shipments/{trackingNumber}/tracking returns the current status, the estimated delivery date and the timeline, oldest first. It carries no internal staff names. note is present only for failed attempts, postponements, cancellation, returns, loss and damage, and holds a reason you can show. location is reserved and not populated yet.

GET /shipments/AWB-RUH-000123/tracking
curl "https://api.goldrock.live/api/public/v1/shipments/AWB-RUH-000123/tracking" \
  -H "X-API-Key: lmc_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
  -H "X-API-Secret: YOUR_API_SECRET"
JSON
{
  "trackingNumber": "AWB-RUH-000123",
  "status": "outForDelivery",
  "statusLabelAr": "خرج للتوصيل",
  "statusLabelEn": "Out For Delivery",
  "estimatedDeliveryDate": "2026-01-17",
  "events": [
    {
      "status": "created",
      "statusLabelAr": "تم إنشاء الطلب",
      "statusLabelEn": "Order Created",
      "at": "2026-01-15T09:30:00Z",
      "note": null,
      "location": null
    },
    {
      "status": "pickedUp",
      "statusLabelAr": "تم الاستلام",
      "statusLabelEn": "Picked Up",
      "at": "2026-01-15T14:05:00Z",
      "note": null,
      "location": null
    },
    {
      "status": "outForDelivery",
      "statusLabelAr": "خرج للتوصيل",
      "statusLabelEn": "Out For Delivery",
      "at": "2026-01-17T07:40:00Z",
      "note": null,
      "location": null
    }
  ]
}

To follow changes without polling, subscribe to webhooks.

GET /shipments/{trackingNumber} returns the full shipment shown above. A shipment that belongs to someone else answers 404 shipment.not_found.

GET /shipments lists shipments, newest first, paginated, with filters that combine with AND: status (one or several, comma separated, as keys or numeric codes), merchant (id or exact name), reference (exact, ignoring case), trackingNumber, recipientPhone (part of it), city (destination: id, code or name), createdFrom and createdTo (ISO 8601) and a free-text search.

GET /shipments
curl -G "https://api.goldrock.live/api/public/v1/shipments" \
  -H "X-API-Key: lmc_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
  -H "X-API-Secret: YOUR_API_SECRET" \
  --data-urlencode 'status=created,outForDelivery' \
  --data-urlencode 'createdFrom=2026-01-01T00:00:00Z' \
  --data-urlencode 'page=1' \
  --data-urlencode 'pageSize=25'
JSON
{
  "items": [
    {
      "trackingNumber": "AWB-RUH-000123",
      "reference": "ORD-1001",
      "status": "outForDelivery",
      "statusLabelAr": "خرج للتوصيل",
      "statusLabelEn": "Out For Delivery",
      "merchant": {
        "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
        "name": "Noor Electronics"
      },
      "senderName": "Noor Electronics",
      "recipientName": "Khaled Alotaibi",
      "recipientPhone": "0555123456",
      "city": {
        "id": "f1e2d3c4-b5a6-4978-8a9b-0c1d2e3f4a5b",
        "nameAr": "الرياض",
        "nameEn": "Riyadh"
      },
      "district": {
        "id": "c2d3e4f5-0a1b-4c2d-8e3f-4a5b6c7d8e91",
        "nameAr": "العليا",
        "nameEn": "Al Olaya"
      },
      "codAmount": 199.5,
      "shippingFee": 30,
      "createdAt": "2026-01-15T09:30:00Z",
      "estimatedDeliveryDate": "2026-01-17"
    }
  ],
  "page": 1,
  "pageSize": 25,
  "totalCount": 1,
  "totalPages": 1
}

GET /shipments/{trackingNumber}/label returns the air waybill as a PDF (100 x 150 mm) with your company's branding. The response is binary: save it, do not parse it as JSON.

GET /shipments/AWB-RUH-000123/label
curl "https://api.goldrock.live/api/public/v1/shipments/AWB-RUH-000123/label" \
  -H "X-API-Key: lmc_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
  -H "X-API-Secret: YOUR_API_SECRET" \
  -o AWB-RUH-000123.pdf

PUT /shipments/{trackingNumber} changes only the fields you send. reason is required (up to 300 characters) and is kept in the shipment's audit trail. At least one other field is needed.

You can change: the order reference, the recipient (name, phones, address by names, coordinates), the parcel (weight, dimensions, pieces, declared value) and the payment (codAmount, freightOnDelivery). When you send address fields, the recipient address is resolved again. You may send only the district: it is then looked up inside the shipment's current city. If you send a city, you must send the district too (400 validation_failed). Places accept an id, a code or a name, as everywhere. The fee is recalculated when something that affects it changes.

You cannot change the sender, the pickup address, the service type and tier or the handling flags. Merchant logins cannot edit shipments.

Editing is allowed until the shipment reaches a final status. Once it is out for delivery, only contact details, the address and COD can change (shipment.field_locked_out_for_delivery).

PUT /shipments/AWB-RUH-000123
curl -X PUT "https://api.goldrock.live/api/public/v1/shipments/AWB-RUH-000123" \
  -H "X-API-Key: lmc_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
  -H "X-API-Secret: YOUR_API_SECRET" \
  -H "Content-Type: application/json" \
  -d '{
  "reason": "Customer changed the delivery address",
  "recipient": {
    "city": "Riyadh",
    "district": "Al Malqa",
    "addressLine": "Anas Bin Malik Road, Villa 7",
    "shortAddress": "RMLA1234",
    "phone": "0555000111"
  },
  "payment": {
    "codAmount": 150
  }
}'

POST /shipments/{trackingNumber}/cancel with an optional reason (up to 500 characters). It is possible while the shipment is a draft, created or scheduled for pickup. Later it answers 422 shipment.cannot_cancel. Check canCancel first. Merchant logins cannot cancel through the API.

POST /shipments/AWB-RUH-000123/cancel
curl -X POST "https://api.goldrock.live/api/public/v1/shipments/AWB-RUH-000123/cancel" \
  -H "X-API-Key: lmc_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
  -H "X-API-Secret: YOUR_API_SECRET" \
  -H "Content-Type: application/json" \
  -d '{
  "reason": "Customer cancelled the order"
}'
JSON
{
  "code": "shipment.cannot_cancel",
  "message": "The shipment can no longer be cancelled in its current status.",
  "status": 422,
  "details": {
    "messageAr": "لا يمكن إلغاء الشحنة في حالتها الحالية."
  },
  "traceId": "00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01"
}
Code Cause
validation_failed A field is missing or malformed. Read details.errors
geo_*_not_found, geo_*_ambiguous A place name did not match, see Places by name
merchant.not_found, merchant.ambiguous The merchant id or name is wrong, or a name is shared by two merchants
coverage.destination_not_covered, coverage.pickup_not_covered The company does not serve that city
branch_coverage.no_coverage_for_city, branch_coverage.ambiguous_coverage Name the pickup branch explicitly
quota.monthly_shipments_limit_reached The company's monthly shipment limit is reached
pricing.default_rate_card_not_found The company has no rate card yet
shipment.cannot_cancel, shipment.not_editable, shipment.field_locked_out_for_delivery The shipment is past the point of that action
idempotency_key_reused The same Idempotency-Key was sent with a different body

See the error reference for every code.