Skip to main content
GET
List Campaign Orders

Overview

The list campaign orders endpoint returns a paginated list of orders attributed to a specific campaign. Use this to see which orders were driven by a given campaign, with optional date range and sorting.

Authentication

This endpoint requires a valid JWT token in the x-auth-token header. You can find your token in the Developers section:

Path Parameters

string
required
The unique identifier of the campaign (MongoDB ObjectId). Only orders attributed to this campaign are returned.

Query Parameters

string
Start date for filtering orders (ISO 8601).
string
End date for filtering orders (ISO 8601).
string
Sort direction: 1 for ascending, -1 for descending. Defaults to -1.
string
Field to sort by: createdAt, name, title, total_messages, cost, revenue, orders_number, campaign_conversion_rate, average_cart, roas.
string
required
Page number (0-based). Use 0 for the first page.
string
required
Number of items per page. Must be at least 1.

Response

The response has two top-level keys: data (array of order objects) and pagination. Each order in data includes order fields (e.g. cms_id, order_number, total, items_number, paid, createdAt) and a populated conversation when available.
array
Array of order documents (TextYess-attributed orders for this campaign).
object
Pagination metadata: total (total count), perPage, page.