What the business paid ShopEazy, fee invoices and recent sales and refunds
- Credentials
- OAuth access token
- Scopes
store:read- Role
- Owners and admins only. Staff get
403 forbidden.
Subscription and credit charges, platform fee invoices, and the recent ledger over the last days days.
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.
days?integer1 <= value <= 36530OK
application/json- response
data*curl -X GET 'https://api.shopeazy.co/v1/merchant/stores/<storeId>/billing/money' \ -H 'Authorization: Bearer <access_token>'{ "data": { "days": 30, "sales": { "amount": 0, "currency": "ZAR" }, "refunds": { "amount": 0, "currency": "ZAR" }, "paidToShopeazy": { "amount": 0, "currency": "ZAR" }, "feeInvoices": [], "ledger": [] }}Book the Launch package on the saved card POST
We set the shop up for the merchant, once per business. Charges the card already on file; a business that already booked it is not charged again (`already: true`). The `Idempotency-Key` keeps a retry from charging twice. `billing:write` is opt-in on the OAuth consent screen. Access: OAuth scope `billing:write`; owner/admin only; write-gated by the subscription.
The business's referral link, credit banked and who signed up through it GET
The link is made on the first ask. A business that subscribes through it gets its next month free; when it pays again the referrer gets a month free too (up to 6 a year). Access: OAuth scope `store:read`; not write-gated.