Docs

List Orders

GET

Query

Uncommon arguments
string

Restricts the list of returned orders to the ones created after (or on) the provided datetime. This parameter should use the following format yyyy-mm-ddThh:MM (year, month, day, 24-hour and minute) and be expressed in UTC time.

string

Restricts the list of returned orders to the ones created before (or on) the provided datetime. This parameter should use the following format yyyy-mm-ddThh:MM (year, month, day, 24-hour and minute) and be expressed in UTC time.

string

Restricts the list of returned orders to the ones whose selected delivery slot lands after (or on) the provided datetime. This parameter should use the following format yyyy-mm-ddThh:MM (year, month, day, 24-hour and minute) and be expressed in UTC time. When this filter is applied, orders that do not have a selected delivery slot (shipped by transporter, for instance) will not be returned. Also, note that a delivery slot is said to land after a given datetime if its slot_start value is later than that datetime.

string

Restricts the list of returned orders to the ones whose selected delivery slot lands before (or on) the provided datetime. This parameter should use the following format yyyy-mm-ddThh:MM (year, month, day, 24-hour and minute) and be expressed in UTC time. When this filter is applied, orders that do not have a selected delivery slot (shipped by transporter, for instance) will not be returned. Also, note that a delivery slot is said to land before a given datetime if its slot_end value comes before that datetime.

string

Restricts the list of returned orders to a certain status. To filter several statuses use the following syntax: ?status={STATUS1}&status={STATUS2}

PaginationRequest a specific window of rows with limit and offset. Learn more
number

Maximum number of rows to return.

number

Number of rows to skip.

Field selectionChoose which fields should be included in the response. Learn more
string

Comma-separated response fields to include.

Every app you connect,one REST pattern

Call any app with one REST pattern. MindCloud handles each provider's auth, request shape, and responses for you.

Learn what the Universal API is
One REST patternUse the same request structure across apps like Slack, HubSpot, Salesforce, and thousands more.
Managed connectionsSend a MindCloud connection ID instead of handling provider tokens, refresh logic, and credential storage yourself.
Action-level docsEach action page shows the exact endpoint, required arguments, optional controls, and response behavior for that app version.