List a customer's orders
Lists a customer's orders, oldest first. The list is offset-based: follow next_page_url or send offset.
Secret tokens, and limited tokens tied to the customer. This is how a signed-in customer sees their order history.
AuthorizationBearer <token>A secret, trusted or limited token. See Authentication.
customer_id*stringThe id of the customer. With a limited token from a customer login you can send me instead.
limit?integerHow many items to return on one page, from 1 to 100. The default is 100. A value outside 1 to 100, or one that is not a whole number, is a 400.
1 <= value <= 100100offset?integerFor offset-based lists, how many items to skip before the page starts. Use next_page_offset or previous_page_offset from the page you have. A value that is not a whole number is a 400.
0 <= value0desc?booleanSort in descending order (newest, largest or last first) when true. The default is false. A value other than true or false is a 400.
falsesort_by?stringThe date to sort by.
"date_created""date_created""date_modified""date_completed"q?stringAn order id. Only that order is returned.
payment_status?stringOnly orders with this payment status.
"unpaid""scheduled""initiated""processing""pending""completed""failed""cancelled""refunded""retry"fulfilled?booleantrue for only fulfilled orders, false for only those not yet fulfilled.
expand?stringComma-separated child objects to return in full instead of as a URL, for example customer,payments. Use dot notation for nested objects (items.product), up to four levels deep. A single object takes up to 12 paths; a list takes up to 2, applied to every item. Extra paths are dropped without an error. See Expanding objects.
show?stringComma-separated fields to return; all others are left out. Use dot notation for child fields (customer.email). You cannot send show and hide together (400). See Customizing output.
hide?stringComma-separated fields to leave out of the response. Use dot notation for child fields (customer.email). You cannot send show and hide together (400). See Customizing output.
formatted?booleanWhen true, the object also has a formatted child with amounts and dates as display text in the shopper's language and currency (for example $19.99 or November 7, 2026). The default is false. See Localized formatting.
falseA page of the customer's orders.
application/json- response
An offset-based list of orders.
total_items*integerThe number of orders in the whole list.
total_pages*integerThe number of pages.
current_page*integerThe page number of this page.
next_page_url*|The URL of the next page, or null on the last page.
next_page_offset*|The offset of the next page, or null.
previous_page_url*|The URL of the previous page, or null on the first page.
previous_page_offset*|The offset of the previous page, or null.
current_page_url*stringThe URL of this page.
data*array<>The orders on this page.
curl -X GET 'https://api.comecero.com/api/v1/customers/string/orders'{ "total_items": 0, "total_pages": 0, "current_page": 1, "next_page_url": null, "next_page_offset": null, "previous_page_url": null, "previous_page_offset": null, "current_page_url": "https://api.comecero.com/api/v1/customers/0091304300408CuoxY9Pf3/orders", "data": []}List a customer's invoices GET
Lists a customer's invoices, oldest first. The list is offset-based: follow `next_page_url` or send `offset`. Secret tokens, and limited tokens tied to the customer. A limited token never sees draft invoices, whatever `draft` says.
List a customer's payment methods GET
Lists the payment methods saved to a customer, oldest first. Every method comes back on one page: `limit`, `offset` and `sort_by` are not used here. Card and bank numbers are never returned, only masks, the last four digits and the brand. Secret tokens, and limited tokens tied to the customer.