POST
/
orders
/
search

Search for all Orders placed through your application given certain filter critera.

This endpoint will only return completed orders by default (no carts). However it is possible to use this endpoint as a “Search Carts” endpoint by combining two parameters. If you wish to include IN_PROGRESS orders AKA carts you can set the exclude_in_progress query param to false.

If you want to use order search to only search for IN_PROGRESS orders, that is to say, searching for carts, you can include the the following query in your search body: {"bag_status": "IN_PROGRESS"}. You must still set exclude_in_progress to false in this case.

Headers

X-Violet-Token
string
X-Violet-App-Secret
string
X-Violet-App-Id
integer

Query Parameters

page
integer
default: 1
size
integer
default: 20
extended
boolean
default: false
exclude_in_progress
boolean
default: true
include
string

Body

application/json
user_id
integer

User ID

order_id
integer

Order ID

referral_id
string

Referral ID

bag_id
integer

Bag ID

bag_status
enum<string>

Bag Status

Available options:
IN_PROGRESS,
SUBMITTED,
ACCEPTED,
COMPLETED,
PARTIALLY_REFUNDED,
REFUNDED,
REJECTED,
CANCELED,
BACKORDERED
merchant_id
integer

Merchant ID

before_date
string

Before date

after_date
string

After date

app_order_id
string

Order ID in the Channels System

Response

default - application/json
content
object[]

The actual content of the response; A list of the result objects

last
boolean

Boolean indicating if this is the last page

total_pages
integer

The total count of pages available

total_elements
integer

The total count of objects available

first
boolean

Boolean indicating if this is the first page of the response

number_of_elements
integer

The total number of objects in this specific response

size
integer

The page size selected at request time

number
integer

The page number selected at request time

empty
boolean

Boolean indicating if the response content is empty

next_page_cursor
string

Contains the cursor for the next page. This property will only be used for situations where the API does not support the page number/page size paradigm and it will mutually exclusive with the size/number fields in the response. If this property is returned it must be passed when requesting the next page from the API. Does not apply to endpoints that do not have a next_page_cursor query param documented.

pageable
object

Violet wrapper for springframework pageable

sort
object

Violet Wrapper for springframework sort