Order management
Find orders that changed, read their current state, and accept, reject, cancel or ship them.
Handling orders is a polling loop: find orders that changed, read each order's current state, and act on it for the seller. You need an access token from the authorization_code flow with scope v2 read write (see Authentication in the API reference) and the Version: 2.0 header on every request.
Endpoint details are in the API reference: Order and Status. The order change feed works like the advert change feed described in Advert and order status synchronization.
-
Discover what changed —
GET /api/partner/status/orders.- Always send
since(ISO-8601 instant with timezone). Optionallycursor(from your previous response'snextCursor) andlimit. - Response:
data(changed order UUIDs, oldest first),hasMore,nextCursor. - Persist
nextCursorafter every poll, even on an empty page, and send it back ascursoron the next call. This is your resume point. - A change is visible only a few seconds after it happened — don't assume same-second consistency.
- This feed returns identifiers only; it never carries order content.
- Always send
-
Fetch the order's current state —
GET /api/partner/orders/{orderId}, for each ID surfaced in step 1 (or on your own polling cadence for orders you already track).- Returns
status,block_reason,items,cost,shipment,buyer_invoice. - This single
statusfield is the seller-facing projection of several independent OLX sub-systems (confirmation, delivery/dispatch, payout, KYC, tax compliance). Field-level detail is in the Order reference.
- Returns
-
Branch on
status:PENDING_CONFIRMATION(hasexpires_at) → seller must accept or reject before the deadline:- Optionally
GET /api/partner/orders/{orderId}/accept-requirementsfirst to see what's still missing (payout_method,payout_details,sender_details,terms_accepted, etc.) before attempting acceptance — avoids a wasted422. - Optionally
GET /api/partner/orders/{orderId}/posting-windowsif you want to offer the seller a pickup-time choice to submit assender_details.posting_windowon accept. POST /api/partner/orders/{orderId}/accept— optionally submits payout method/details, sender details, and terms acceptance in the same call. Returns204on success, or422withrequired_actionsif preconditions are still unmet.POST /api/partner/orders/{orderId}/reject— terminal; requires areason(see the Order reference for the enum). Use this instead of cancel for anything not yet accepted.
- Optionally
AWAITING_SHIPMENTandshipment.label_available: true→GET /api/partner/orders/{orderId}/labelto download the shipping-label PDF and hand the parcel to the carrier.PAYOUT_BLOCKEDwith ablock_reason→ surface the reason to the seller (IDENTITY_VERIFICATION_REQUIRED/_IN_PROGRESS/_FAILED, orTAX_COMPLIANCE_REQUIRED) and poll again later; there is no partner API call that resolves this — the seller resolves it through the OLX consumer-facing verification flow.- Any state where the seller can no longer fulfill (out of town, item already sold elsewhere,
etc.) and the order was already accepted →
POST /api/partner/orders/{orderId}/cancelwith areason. Cancellation of an order stillAWAITING_SHIPMENTmay be asynchronous — re-poll order details to observe the resulting state. PENDING_CONFIRMATIONorders cannot be cancelled —cancelon such an order returns422 ORDER_NOT_CANCELLABLEwith a hint to userejectinstead.
-
Loop. Keep polling the status feed on a schedule with your saved cursor; re-fetch order details whenever an ID reappears.