One page: its draft, what is live, its settings and a preview link
- Credentials
- OAuth access token
- Scopes
store:read
previewUrl is a private link valid for 2 hours, or null when this deployment cannot sign one.
Access: OAuth scope store:read; 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.
pageId*stringA page id from listPages.
OK
application/json- response
data*curl -X GET 'https://api.shopeazy.co/v1/merchant/stores/<storeId>/pages/<pageId>' \ -H 'Authorization: Bearer <access_token>'{ "data": { "id": "string", "title": "string", "slug": "string", "live": true, "unpublishedChanges": true, "inMenu": true, "inFooter": true, "catalogPage": "physical", "draft": { "title": "string", "blocks": [ {} ] }, "liveBlocks": [ { "id": "string", "type": "string", "heading": "string" } ], "menuLabel": "string", "seo": {}, "previewUrl": "string", "previewExpiresAt": 0 }}The order pages appear in the menu and footer PUT
Page ids, first to last. Pages left out keep their place after these. Access: OAuth scope `design:write`; owner/admin only; write-gated by the subscription.
A page's title, address, menu and footer placement and menu label PATCH
Address and menu changes are live at once; a new title is saved in the draft and goes live with `publishPage`. A live page that moves keeps answering at its old address. Access: OAuth scope `design:write`; owner/admin only; write-gated by the subscription.