Kurly · Arazzo Workflow
Kurly delivery-agency order through to delivery tracking
Version 1.0.0
Authenticate against KLS, confirm the shipper's contracted delivery services, register a delivery-agency order with a caller-supplied requestKey, read the order back by that key, pull the waybill print data, and track the resulting shipment. Grounded in the operations captured in openapi/, reconstructed from https://developers.kurly.com.
View Spec
View on GitHub
CompanyTechnologyLogisticsFulfillmentSupply ChainDeliveryE-CommerceGroceryShippingOrder ManagementInventoryTrackingSouth KoreaArazzoWorkflows
Provider
Workflows
registerDeliveryOrderAndTrack
Register a delivery-agency order idempotently and follow it to delivery.
requestKey is supplied by the caller so that a retry of step registerOrder cannot double-register the shipment. Kurly does not push events, so tracking is polled.
1
2
listDeliveryPolicies
Confirm which delivery services the shipper is contracted for before registering.
3
registerOrder
Register the delivery-agency order. Retry this step with the SAME requestKey — never a fresh one. Delivery date must be within D+1.
4
confirmOrderByRequestKey
Authoritative check after an ambiguous retry — if the order is present, it registered and must not be sent again. Accepts up to 50 keys.
5
getInvoicePrintData
Retrieve waybill print data and capture the invoice number used for tracking.
6
trackShipment
Poll tracking. Stop only on DELIVERY_COMPLETED or DELIVERY_FAILED; intermediate stages may be skipped, so never require the full sequence.
Source API Descriptions
openapi
openapi
openapi
deliveryTrackingApi
https://artifacts.apis.io/kurly/openapi/kurly-delivery-tracking-api-openapi.yml
Arazzo Workflow Specification
Work with this as data
Every workflow here is available over the APIs.io API and to AI agents over MCP.