Recent conversations
- Credentials
- OAuth access token
- Scopes
messages:read
Needs messages:read.
Access: OAuth scope messages:read (a grant with messages:send passes too); not write-gated.
Paged: { items, nextCursor }, limit (default 50, at most 100) and an opaque cursor. It pages through the newest 100.
merchantOAuth messages: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: messages:read
storeId*stringA store the person can reach. Any other id answers 404, never 403.
cursor?stringThe nextCursor of the previous page, unchanged. A cursor that is not one we gave you is 400 bad_request.
limit?integerPage size: default 50, at most 100 (more is 100; a missing or unusable value is 50).
1 <= value <= 10050OK
application/json- response
data*curl -X GET 'https://api.shopeazy.co/v1/merchant/stores/<storeId>/whatsapp/threads' \ -H 'Authorization: Bearer <access_token>'{ "data": { "items": [], "nextCursor": null }}Switch the WhatsApp AI auto-reply on or off PUT
It answers customers in the merchant's name, so it is off until the owner or an admin turns it on, and a connected AI app can only do so with `settings:write`. Setting the value it already has changes nothing. `enabled` must be `true` or `false`, else 400 `bad_request`. `getWhatsAppChannel` reports it as `aiEnabled`. Access: OAuth scope `settings:write`; owner/admin only; write-gated by the subscription.
One conversation and its messages GET
Access: OAuth scope `messages:read` (a grant with `messages:send` passes too); not write-gated.