Delivery-agency order through to delivery tracking
A 6-step recipe with Kurly. We can help you get access.
Recipe · 6 steps
Delivery-agency order through to delivery tracking
with Kurly · Shipment Tracking Management
Register a delivery-agency order idempotently and follow it to delivery.
- Exchange clientId and secretKey for a Bearer access token.
- Confirm which delivery services the shipper is contracted for before registering.
- Register the delivery-agency order. Retry this step with the SAME requestKey — never a fresh one. Delivery date must be within D+1.
- Authoritative check after an ambiguous retry — if the order is present, it registered and must not be sent again. Accepts up to 50 keys.
- Retrieve waybill print data and capture the invoice number used for tracking.
- Poll tracking. Stop only on DELIVERY_COMPLETED or DELIVERY_FAILED; intermediate stages may be skipped, so never require the full sequence.
What you'll need to have ready
- clientId: Issued by Kurly after IP allowlist registration.
- secretKey: Issued by Kurly after IP allowlist registration.
- requestKey: Caller-generated idempotency and identity key, unique per shipper and never reusable.
- clientOrderCode: Optional sales-channel order number; may be duplicated, not an identifier.
- courier: Carrier code, e.g. Kurly Nextmile.
For your developer
Arazzo workflow kurly:registerDeliveryOrderAndTrack, 6 operations: issueToken → findDeliveryPolicies → createDeliveryOrder → findDeliveryOrdersByRequestKeys → findInvoicePrintData → findDeliveryTracking. Specs on APIs.io.