Store details, channels and go-live blockers
- Credentials
- OAuth access token
- Scopes
store:read- Role
- Owners and admins only. Staff get
403 forbidden.
Access: OAuth scope store:read; owner/admin only; 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.
OK
application/json- response
data*curl -X GET 'https://api.shopeazy.co/v1/merchant/stores/<storeId>/profile' \ -H 'Authorization: Bearer <access_token>'{ "data": { "id": "w82oaN7OkGK7BykWs2Ag", "name": "Jabu's Plant Shop", "subdomain": "jabus-plant-shop", "description": null, "supportEmail": null, "supportPhone": null, "location": null, "branding": { "logoUrl": null, "primaryColor": "#e63946" }, "channels": { "storefront": true, "whatsapp": false }, "directoryListed": true, "categoryCode": "home_garden", "blockers": [] }}What a store can say it sells (the store category choices) GET
Send a `code` as `categoryCode` to updateStoreProfile: the storefront cannot go live without one. Access: OAuth scope `store:read`; not write-gated. Paged: `{ items, nextCursor }`, `limit` (default 100, at most 200) and an opaque `cursor`.
Edit store details and switch channels on PATCH
Access: OAuth scope `settings:write`; owner/admin only; write-gated by the subscription.