What is going in the box, and what it will be billed at
- Credentials
- OAuth access token
- Scopes
orders:read
Shown before booking a courier. Only lines that need shipping count; lineIds narrows it to the lines of one parcel of a split order. Nothing is quoted or booked: quoteDelivery prices it and bookCollection books it. A read, so it is not write-gated.
Access: OAuth scope orders:read; not write-gated.
merchantOAuth orders: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: orders:read
storeId*stringA store the person can reach. Any other id answers 404, never 403.
orderId*stringlineIds?stringComma-separated line ids of the order. Default: every line that needs shipping.
OK
application/json- response
data*curl -X GET 'https://api.shopeazy.co/v1/merchant/stores/<storeId>/orders/<orderId>/delivery/parcel-preview' \ -H 'Authorization: Bearer <access_token>'{ "data": { "parcels": [ { "description": "string", "lengthCm": 0, "widthCm": 0, "heightCm": 0, "weightKg": 0, "chargeableKg": 0, "volumetricKg": 0 } ], "totalChargeableKg": 0, "usingDefaultFor": [ "string" ], "unmeasurable": true }}Email the waybill to the merchant POST
Access: OAuth scope `delivery:write`; write-gated by the subscription.
Find courier lockers and counters GET
Neither `q` nor a point returns `lockers: []`. A read, so it is not write-gated: a store whose plan has lapsed can still search. Access: OAuth scope `orders:read`; not write-gated.