List orders

What is it for?

Returns a list of orders. You can filter by several criteria. All parameters are optional — without parameters it returns all orders.

Conditions

  • Requires authentication.

Parameters

Fill in the fields in Query Params and/or Path Params as applicable.

Quick parameter guide

  • ids: Filter by specific order IDs (Instructions: The IDs you got when creating orders. Separate with commas: 1,2,3)
  • status_ids: Filter by order status (Instructions: Check with your team for the available status IDs. Separate with commas)
  • shop_ids: Filter orders from specific shops (Instructions: Call GET /api/v1/client/shops → copy the "id" of the shops you want. Separate with commas)
  • payment_method_ids: Filter by payment method (Instructions: Call GET /api/v1/client/payment-methods → copy the "id". Separate with commas)
  • courier_ids: Filter by courier (Instructions: Check with your team for the available courier IDs. Separate with commas)
  • date[column]: Which date field to use for filtering (Instructions: Write one of these values: order_created_at, processed_at, last_shipment_update)
  • date[start]: Start date of the range (Instructions: Formato: 2024-01-01)
  • date[end]: End date of the range (Instructions: Formato: 2024-01-31)
  • search: Text search (Instructions: Type the reference, ID or tracking number you are looking for)
  • product_ids: Filter orders containing those products (Instructions: Call GET /api/v1/client/products → copy the "id". Separate with commas)
  • sorting[column]: Field to sort by (Instructions: Possible values: id, ref, order_created_at, processed_at, last_shipment_update)
  • sorting[direction]: Ascending or descending order (Instructions: Write: asc or desc)
  • per_page: How many orders to show per page (Instructions: An integer. Default is usually 15 or 25)
  • page: Which page to view (Instructions: Starts at 1)

Expected response

HTTP 200 → Paginated list of orders with pagination data

Order Status Reference

The status_id field can have the following values:

idDescription (ES)Meaning
1Por confirmarOrder created, not yet confirmed by the client
2PendienteOrder pending processing
3Por prepararOrder ready to start picking
4PickingPicking in progress
5PackingPacking in progress
6PreparadoOrder prepared, ready to ship
7EnviadoOrder shipped to courier
8DevueltoOrder returned by customer
9CanceladoOrder cancelled

Note: The description field in the response contains the Spanish text shown above. The status_id and status.id fields share the same numeric domain.

Shipment Status Reference (Normalized)

The fields shipment.status_mapped_id and shipment_status.id use the following normalized values, independent of the courier:

idName (ES)Meaning
1Sin estado logísticoNo logistics status assigned yet
2En TránsitoShipment in transit
3En RepartoOut for delivery
4Punto de recogidaAt pickup point
5EntregadoDelivered
6Devuelto al RemitenteReturned to sender
7CanceladoCancelled
8SiniestroIncident / damaged in transit
9ReexpedidoForwarded / re-shipped
10DestruidoDestroyed

Note: These values may be null when the courier returns a status code that has not yet been mapped internally.

External Financial Status Reference

The external_financial_status field reflects the financial state coming from the external e-commerce platform (Shopify, WooCommerce, MercadoPago). Accepted values:

ValueMeaning
paidOrder has been paid
pendingOrder pending payment
refundedOrder has been refunded
partially_refundedOrder has been partially refunded

Note: When sent in a request (POST/PUT), the value is accepted as free string and stored as-is.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Query Params
string
^[0-9,]+$

Filter by specific order IDs

Instructions: The IDs you got when creating orders. Separate with commas: 1,2,3

string
^[0-9,]+$

Filter by order status. Accepts the same values as the status_id field in the response (1-9). Separate multiple values with commas (e.g. '1,2,3'). See the Order Status Reference table in the endpoint description.

string
^[0-9,]+$

Filter orders from specific shops

Instructions: Call GET /api/v1/client/shops → copy the "id" of the shops you want. Separate with commas

How to obtain it: use List shops.

string
^[0-9,]+$

Filter by payment method

Instructions: Call GET /api/v1/client/payment-methods → copy the "id". Separate with commas

string
^[0-9,]+$

Filter by courier

Instructions: Check with your team for the available courier IDs. Separate with commas

string
enum

Which date field to use for filtering

Instructions: Write one of these values: order_created_at, processed_at, last_shipment_update

Allowed:
date

Start date of the range

Instructions: Formato: 2024-01-01

date

End date of the range

Instructions: Formato: 2024-01-31

Text search

Instructions: Type the reference, ID or tracking number you are looking for

string
^[0-9,]+$

Filter orders containing those products

Instructions: Call GET /api/v1/client/products → copy the "id". Separate with commas

How to obtain it: use List products.

string
enum

Field to sort by

Instructions: Possible values: id, ref, order_created_at, processed_at, last_shipment_update

Allowed:
string
enum

Ascending or descending order

Instructions: Write: asc or desc

Allowed:
integer
≥ 1

How many orders to show per page

Instructions: An integer. Default is usually 15 or 25

integer
≥ 1

Which page to view

Instructions: Starts at 1

advanced_filters
object

Advanced filters in JSON format.

Responses

400

Bad request

401

Unauthorized (invalid or expired token)

422

Validation error

Language
Credentials
Basic
base64
:
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json