{ "opencollection": "1.0.0", "info": { "name": "Commerce Layer addresses carts API", "version": "7.10.1" }, "request": { "auth": { "type": "bearer", "token": "{{bearerToken}}" } }, "items": [ { "info": { "name": "carts", "type": "folder" }, "items": [ { "info": { "name": "Query breakdown on carts", "type": "http" }, "http": { "method": "POST", "url": "https://{your_organization_slug}.commercelayer.io/api/carts/breakdown", "body": { "type": "json", "data": "{}" } }, "docs": "Breakdowns are aggregations that summarize your data as metrics (based on specific operators) or statistics, computed on field values. When performing a breakdown query on the Metrics API endpoint you get in the response the value of the computation (based on the selected operator) on the selected field, aggregated by another field.\r\n\r\n### Nesting breakdowns\r\nBreakdowns can be nested recursively one into the other, up to one level (see example). The valid values allowed for the by key of the nes" }, { "info": { "name": "Query date_breakdown on carts", "type": "http" }, "http": { "method": "POST", "url": "https://{your_organization_slug}.commercelayer.io/api/carts/date_breakdown", "body": { "type": "json", "data": "{}" } }, "docs": "Date breakdowns summarizes metrics data grouped by time intervals on a defined time range. They also support support breakdowns over the main date breakdown query and also supports all breakdown queries capabilities through the \"breakdown\" key, this also includes the possibility of nesting the breakdown over the main breakdown. \r\n\r\n\r\nSingle date breakdown request (no breakdown)\r\n\r\n`{\r\n\t\"date_breakdown\": {\r\n \"by\": \"order.created_at\",\r\n \"field\": \"order.total_amount_with_taxes\",\r\n " }, { "info": { "name": "Query stats on carts", "type": "http" }, "http": { "method": "POST", "url": "https://{your_organization_slug}.commercelayer.io/api/carts/stats", "body": { "type": "json", "data": "{}" } }, "docs": "Stats are aggregations that summarize your data within an operator (depending of the field, some of them could not be available), such as: value_count, cardinality, avg, min, max, sum or stats (which returns avg, min, max, sum) computed on the field specificed. When performing a stats query on the Metrics API endpoint you get in the response the value of the computation (based on the selected operator) on the selected field.\r\n\r\nStats request\r\n\r\n`{\r\n\t \"stats\": {\r\n \"field\": \"order.total_amo" }, { "info": { "name": "Query search on carts", "type": "http" }, "http": { "method": "POST", "url": "https://{your_organization_slug}.commercelayer.io/api/carts/search", "body": { "type": "json", "data": "{}" } }, "docs": "Get search results from carts" }, { "info": { "name": "Query export on carts", "type": "http" }, "http": { "method": "POST", "url": "https://{your_organization_slug}.commercelayer.io/api/carts/export", "body": { "type": "json", "data": "{}" } }, "docs": "Get export results from carts" } ] } ], "bundled": true }