Orders Core
Overview
The Orders Core API provides fundamental operations for managing orders in SellerCenter. Orders represent customer purchases and contain order items, customer information, shipping details, and payment information.
Core order operations include:
- Order listing: Retrieve collections of orders with extensive filtering options
- Order anonymization: Anonymize customer information in orders for GDPR/LGPD compliance
- Order retrieval: Get detailed information about specific orders
- Order search: Search orders and get autocomplete suggestions
- Order counters: Get approximate counts of orders by status
Important: Orders can be filtered by many criteria including status, dates, customer information, shipment details, and more. The counters endpoint provides eventually consistent data suitable for UI hints and dashboards.
Get List of Orders
GET /v2/orders
Summary: Get list of orders with filters
Description: Retrieve a paginated collection of orders with extensive filtering capabilities. This endpoint supports filtering by status, dates, order numbers, customers, shipment types, payment methods, and many other criteria.
Parameters:
X-Context(header, optional): Context header (adminorseller)limit(query, required): Maximum number of items to returnoffset(query, required): Number of items to skipsection(query, optional): Search section (e.g.,status_shipped,status_delivered,status_pending,group_economy, etc.)packed(query, optional): Search by packed status (fully_packed,partially_packed,not_packed)customers[](query, optional): Search by customer name (first name and last name)printedStatus(query, optional): Search by printed statustags[](query, optional): Search by tag's numeric idproductSku[](query, optional): Search by product skudelivery(query, optional): Search by delivery (shippedUnder24h,notShippedUnder24h,notShippedUnder24BusinessHours)shipmentType(query, optional, deprecated): Search by shipment type (warehouse,dropshipping,crossdocking). UseshipmentTypes[]instead.shipmentTypes[](query, optional): Search by shipment types (array;warehouse,dropshipping,crossdocking)shipmentProviders[](query, optional): Search by shipment provider idpaymentMethods[](query, optional): Search by payment methodsoutlet(query, optional): Search orders from outlet onlyinvoiceRequired(query, optional): If set to "1", only orders requiring invoice will be returnedcancelationReasons[](query, optional, deprecated): Search by cancelation reason idcancelationReasonIds[](query, optional): Search by cancelation reason idfulfilmentType[](query, optional): Search by fulfilment type (merchant,venture)orderSources[](query, optional): Search by order sourcessellerNames[](query, optional): Search by seller namessellerIds[](query, optional): Search by seller IDsupdateDateStart(query, optional): Filter orders updated after this dateupdateDateEnd(query, optional): Filter orders updated before this datewarehouses[](query, optional): Search by warehouse IDsincludeVoucherDetails(query, optional): Include voucher details in responseincludeProductSet(query, optional): Include product set informationdateStart(query, optional): Search by order creation date or date timedateEnd(query, optional): Search by order creation date or date timeorderNumbers[](query, optional): Filter by order numbers (array)orderIds[](query, optional): Search by order IDssort(query, optional): Sort field (createdAtorupdatedAt)sortDir(query, optional): Sort direction (ascordesc)
Note:
- Supports extensive filtering by status, dates, customers, shipment types, payment methods, and many other criteria
- Returns paginated results with
limit,offset,total, andhasNextfields - Use
X-Contextheader to specify admin or seller context - Multiple filters can be combined for precise order retrieval
Anonymize Order Information
POST /v2/orders/anonymize
Summary: Anonymize order information
Description: Anonymize customer information in one or more orders for GDPR/LGPD compliance. This endpoint supports two modes:
- Default Mask Mode: When
default_maskis provided, all customer data fields (names, addresses, etc.) will be replaced with the mask value. - Selective Update Mode: When specific fields are provided without
default_mask, only those fields will be updated.
The operation processes orders in batch and returns detailed results for each order.
Request Body:
order_numbers(array, required): Array of order numbers to anonymize (minimum 1 item)default_mask(string, optional): Default mask to apply to all fields if providedaddress_billing(object, optional): Billing address fields to updatefirst_name,last_name: Customer names for billingphone,phone2: Primary and secondary phone numbersaddress1toaddress5: Address linescity,postcode,country: Location detailscustomer_email: Email address for billing
address_shipping(object, optional): Shipping address fields to update (same structure as billing)customer_first_name(string, optional): Customer's first namecustomer_last_name(string, optional): Customer's last namenational_registration_number(string, optional): National registration number
Examples:
- Default mask: Apply "LGPD-1212" to all customer data fields
- Selective update: Update only specific fields like customer names and billing address
- Batch processing: Process multiple orders in a single request
Response Codes:
- 200: All orders processed successfully
- 206: Partial success - some orders processed, others failed
- 400: Bad request - validation errors or all orders failed
Note:
- Supports batch processing of multiple orders
- Returns detailed success/failure information for each order
- Useful for GDPR/LGPD compliance requirements
- When using
default_mask, all customer fields are replaced with the mask value
Get Order by ID
GET /v2/orders/{orderId}
Summary: Get a specific order by ID
Description: Retrieve detailed information about a specific order by its numeric ID. Returns complete order information including order items, customer details, shipping information, and payment details.
Parameters:
orderId(path, required): Numeric ID of the ordershipmentType(query, optional): Filter by shipment typeincludeProductSet(query, optional): Include product set information
Note:
- Returns complete order details including all order items
- Use
includeProductSetto get additional product set information - Order status and history information is included in the response
Search Orders
GET /v2/orders/search
Summary: Search orders for autocomplete suggestions
Description: Search orders and get autocomplete suggestions for order numbers, order sources, customers, and products. Useful for building search interfaces and autocomplete functionality.
Parameters:
key(query, required): Search key type (order_number,order_nr,order_source,customer,product,cancelation-reason)query(query, required): Search query stringfilteredStatus(query, optional): Filter by status (various status options available)
Note:
- Returns autocomplete suggestions based on the search key type
- Supports searching by order number, order source, customer, or product
- Useful for building search interfaces with autocomplete
Get Order Counters
GET /v2/orders-counters
Summary: Get order counter values for each order state
Description: Get approximate counters for orders grouped by filters. This endpoint is suitable for getting quick information about count of orders, for example, when developing your own UI and want to display hints with count of pending orders. Data is eventually consistent, however there can be some delay in updating those counters.
Parameters:
includeOrderCounters(query, optional): When set to false, excludes order counters from response (default:true)includeReturnCounters(query, optional): When set to true, includes return counters (default:false)
Note:
- Returns counters for pending, ready_to_ship, shipped, delivered, cancelled orders
- Data is eventually consistent - may have slight delays
- Use
includeReturnCountersto get return-related counters - Suitable for dashboard displays and UI hints