Which events draft a social post by themselves
- Credentials
- OAuth access token
- Scopes
marketing:read
Read from the store's settings; a store that never saved any answers the defaults (all four on). A read, so a store whose plan has lapsed can still read it.
Access: OAuth scope marketing:read; not write-gated.
merchantOAuth marketing: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: marketing:read
storeId*stringA store the person can reach. Any other id answers 404, never 403.
OK
application/json- response
data*Which events draft a social post by themselves. They are only ever drafts: nothing goes out until it is approved (publishSocialPost, scheduleSocialPost). All four default to true.
curl -X GET 'https://api.shopeazy.co/v1/merchant/stores/<storeId>/social/automation' \ -H 'Authorization: Bearer <access_token>'{ "data": { "newProduct": true, "priceDrop": true, "backInStock": true, "discount": true }}Post a free-text message to the shop's Facebook Page, now POST
Publishes at once, publicly, to the connected Page: `createSocialPost` and `publishSocialPost` post about listings, this posts whatever the merchant wrote. Needs a connected Page (`getFacebookPage`): without one 409 `facebook_not_connected`; a Page whose token Meta no longer accepts is 422 `provider_error` and the channel shows as broken in `getFacebookPage` (`status: error`, `lastError`) so posting never fails silently. Facebook's own words for a refusal come back in the message, quoted as Facebook's. The `Idempotency-Key` is what keeps a retry from posting twice: it is written down before Facebook is called, so a replay returns the first answer and posts nothing, even after a lost answer or a crash. Facebook busy (429) or down (5xx, or no answer) is 503 `provider_unavailable` with `Retry-After`, never 500. When Facebook answered busy nothing was posted and the same key may be sent again; when it did not answer, or failed, the post may already be on the Page, so the same key is held (409 `in_flight`): look at the Page, and use a new key to send it again. Access: OAuth scope `marketing:write`; write-gated by the subscription.
Save which events draft a social post by themselves PUT
Replaces all four switches; send all four. Saving the same values again changes nothing. Needs a connected Facebook Page. Access: OAuth scope `marketing:write`; write-gated by the subscription.