Sales by product, month, channel or seller
- Credentials
- OAuth access token
- Scopes
store:read- Role
- Owners and admins only. Staff get
403 forbidden. - Add-on
- Analytics plus
The same tables as the console's Reports page. rows follow by. Products are capped at 50.
Plan: Analytics Plus (included with Growth and Scale), else 403 plan_limit. The console shows the same figures on its Sales, Products, Customers and Traffic pages only with it.
Access: OAuth scope store:read; owner or admin; not write-gated.
merchantOAuth store:readAuthorizationBearer <token>OAuth 2.1 (authorization code + PKCE S256, public clients, dynamic registration) for connected AI apps. Effective power is scopes granted AND the person's role today AND the plan. orders:refund, billing:write and team:write are opt-in on the consent screen. Write implies read for marketing:read and messages:read, so a grant holding marketing:write passes a marketing:read check, and messages:send passes messages:read.
Scope: store:read
storeId*stringA store the person can reach. Any other id answers 404, never 403.
by*string"product""month""channel""person"days?integerHow many days back, up to now.
1 <= value <= 73090OK
application/json- response
data*curl -X GET 'https://api.shopeazy.co/v1/merchant/stores/<storeId>/reports/sales?by=product' \ -H 'Authorization: Bearer <access_token>'{ "data": { "by": "product", "days": 30, "rows": [] }}Visitors to the shop and what they searched for GET
From the storefront's own daily tracking. Plan: Analytics Plus (included with Growth and Scale), else 403 `plan_limit`. The console shows the same figures on its Sales, Products, Customers and Traffic pages only with it. Access: OAuth scope `store:read`; owner or admin; not write-gated.
Drafts, scheduled and sent posts, newest first GET
Access: OAuth scope `marketing:write`; not write-gated. Paged: `{ items, nextCursor }`, `limit` (default 20, at most 50) and an opaque `cursor`. It pages through the newest 50.