Suppliers, A to Z
- Credentials
- OAuth access token
- Scopes
listings:read
Access: OAuth scope listings:read; not write-gated.
Paged: { items, nextCursor }, limit (default 100, at most 200) and an opaque cursor.
merchantOAuth listings: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: listings: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 100, at most 200 (more is 200; a missing or unusable value is 100).
1 <= value <= 200100OK
application/json- response
data*curl -X GET 'https://api.shopeazy.co/v1/merchant/stores/<storeId>/suppliers' \ -H 'Authorization: Bearer <access_token>'{ "data": { "items": [], "nextCursor": null }}Remove someone from the team DELETE
Takes away their access and any AI connections they made. You cannot remove yourself. Team changes need the opt-in scope `team:write`, and the person's own role: owner or admin. An admin manages staff only; nobody changes the owner. Access: OAuth scope `team:write`; owner/admin only; write-gated by the subscription.
Add a supplier POST
Scale. Plan: Scale (403 `plan_limit` on a plan without it). Reading and changing what already exists stays open after a downgrade. Access: OAuth scope `listings:write`; write-gated by the subscription.