Skip to content

Read customer stats

Reads the store's customer stats over a period.

Needs the customer:read scope.

Call

  • Tool: customer_stats
  • Scope: customer:read
  • Reads only.
  • Acts on a store.

Arguments

Name Type Required Description
store string No The store to act on.
from string No
to string No
bucket "day" or "week" or "month" No
{
  "type": "object",
  "properties": {
    "store": {
      "type": "string",
      "description": "The store to act on."
    },
    "from": {
      "type": "string",
      "format": "date"
    },
    "to": {
      "type": "string",
      "format": "date"
    },
    "bucket": {
      "type": "string",
      "enum": [
        "day",
        "week",
        "month"
      ]
    }
  },
  "additionalProperties": false
}

Answer

Name Type Required Description
customers object Yes
new_customers object Yes
returning object Yes
spent array of object Yes
all_time object Yes
by_country array of object Yes
series array of object Yes
bucket string Yes
time_zone string Yes
from string Yes
to string Yes
previous_range object Yes

The answer’s full shape is on its API reference page.

Errors

A refused call is a tool error. Its structuredContent holds a code and its context, except for client-fault. This tool may answer:

  • invalid: an argument is malformed; context.path names it.
  • invalid at ["store"]: store is missing while the connection reaches more than one store, or names a store it doesn’t reach.
  • not_permitted: this connection may not make this call. When context.reason is limit, too many calls: retry_after says when to try again.
  • internal or unavailable: the call failed inside Sherpo. A read marked transient may be retried.
  • client-fault: the server failed around the call. reached_core says whether it reached Sherpo; the call may be made again.
  • HTTP 403 with insufficient_scope: the connection lacks the scope this tool needs.
  • HTTP 401 with invalid_token: the access token expired or the connection ended. Refresh the token, and connect again if the refresh fails or the new token is refused too.

Any other code may come back too, such as a conflict when the state changed under the call. When the answer was already streaming, a 401 or 403 comes back as a tool error with only its text. See Errors for every code and its context.

Type to search…

↑↓ navigate↵ selectEsc close