Enabled resource errors field for orders and carts —
Check the use case
Changelog

Search

How to perform a search query and how it works

Searches are a type of query a bit different from the other ones (breakdowns, date breakdowns, and stats). A search is not an aggregation and doesn't involve any computation based on operators, but an actual search. When performing a search query on the Metrics API endpoint you get in the response the list of the requested fields (sorted, filtered, and paginated) of the actual records that match the query.

Request

To perform a search query send a POST request to the /{{resource_name}}/search endpoint specifying the query keys and filter parameters:

{
  "search": {
    "limit": ...,
    "sort": "...",
    "sort_by": "...",
    "fields": [ ... ],
    "cursor": "..."
  },
  "filter": { ... },
  "meta": { ... }
}

Query keys

Key
Type
Required
Description
Values

limit

Integer

The maximum number of records shown in the response.

Default is 50, max is 100.

sort

String

The way you want the results of the query to be sorted.

One of asc or desc (default is desc).

sort_by

String

The date field you want the results of the query sorted by.

The available values for this key depend on the resource you're searching (see orders, returns, or carts for the related lists). Default is {{resource_name}}.current_date (i.e. the datetime of the resource's latest status change).

fields

Array

The list of fields you want to be returned for each record in the response.

The available values for this key depend on the resource you're searching (see orders, returns, or carts for the related lists). Cannot be empty. Use {{field_name}}.* to request all the field's attributes.

cursor

String

The cursor pointing to a specific page in the paginated search results.

Every time you perform a search query you get the cursor to the next page in the pagination object.

Requesting all the field's attributes

In some cases, you may need to get in the search results all the attributes of some fields for each record. If so, you can use the .* syntax in the request. Just add {{field_name}}.* to the field array for each field you want to fully detail (see example).

Response

The response of a search query returns an array of objects containing a number of records equal to (or less than) the one specified in the limit key, sorted by the date field specified in the sort_by key. For each record all the fields requested in the fields array are returned:

{
  "data": [
    { 
      "...": "...", // requested fields
      "...": "...",
      "...": { ... }
      "...": ...
    },
    { 
      "...": "...", // requested fields
      "...": "...",
      "...": { ... }
      "...": ...
    },
    { 
      "...": "...", // requested fields
      "...": "...",
      "...": { ... }
      "...": ...
    },
    { ... }
  ],
  "meta": {
    "pagination": {
      "record_count": ...,
      "cursor": "..."
    },
    ...
  }
}

Pagination

Unlike the other types of queries (breakdowns, date breakdowns, and stats) when performing a search query on the Metrics API endpoint you get paginated results. You can find the info you need to navigate through the pages in the pagination object of the response's meta:

Field
Type
Description

record_count

Integer

The total number of records that match the query.

cursor

String

The cursor pointing to the next page (null if record_count < limit).

The value of the cursor can be added to the request payload to get that specific page's records in the response (see example).

Examples

Requesting specific fields

The following request performs a search query to get information about the orders total amount, currency, alongside the associated customer email and shipping address information, sorted by the time when they were placed:

curl -g -X POST \
  'https://{{your_domain}}.commercelayer.co/metrics/orders/search' \
  -H 'Accept: application/vnd.api.v1+json' \
  -H 'Content-Type: application/vnd.api+json' \
  -H 'Authorization: Bearer {{your_access_token}}' \
  -d '{
    "search": {
      "limit": 5,
      "sort": "desc",
      "sort_by": "order.placed_at",
      "fields": [
        "order.id",
        "order.number",
        "order.placed_at",
        "order.total_amount_with_taxes",
        "order.currency_code",
        "customer.email",
        "shipping_address.state_code",
        "shipping_address.zip_code"
      ]
    }
  }'

Requesting all the attributes for some fields

The following request performs a search query to get all the available fields for the last two orders placed and the associated customers:

curl -g -X POST \
  'https://{{your_domain}}.commercelayer.co/metrics/orders/search' \
  -H 'Accept: application/vnd.api.v1+json' \
  -H 'Content-Type: application/vnd.api+json' \
  -H 'Authorization: Bearer {{your_access_token}}' \
  -d '{
      "search": {
        "limit": 2,
        "sort": "desc",
        "sort_by": "order.placed_at",
        "fields": [
          "order.*",
          "customer.*"
        ]
      }
  }'

Requesting a specific page from the paginated results

The following request performs a search query to get information about the number of shipments associated with the orders and their fulfillment status, sorted by the time of the last fulfillment status update. A specific page in the paginated results is requested:

curl -g -X POST \
  'https://{{your_domain}}.commercelayer.co/metrics/orders/search' \
  -H 'Accept: application/vnd.api.v1+json' \
  -H 'Content-Type: application/vnd.api+json' \
  -H 'Authorization: Bearer {{your_access_token}}' \
  -d '{
      "search": {
        "limit": 5,
        "sort": "desc",
        "sort_by": "order.fulfillment_updated_at",
        "fields": [
          "order.id",
          "order.number",
          "order.shipments_count",
          "order.fulfillment_status",
          "order.fulfillment_updated_at"
        ],
        "cursor": "LS0tCi0gJzIwMjItMDYtMjZUMDY6MD=="
      }
  }'
PreviousStatsNextFilters

Last updated