The signed-in shopper's upcoming bookings at this store
- Credentials, one of
- Store key and Shopper session
- Store key and Shopper ID token
- Scopes
orders:read
Soonest first. One row per booked service line on the caller's orders, from now on. Lines on cancelled orders are left out.
Paged: { items, nextCursor }, limit (default 50, at most 100) and an opaque cursor.
Old path, deprecated, sunset 1 Feb 2027: GET /v1/me/bookings.
AuthorizationBearer <sez_pub_... (publishable) or sez_sk_... (secret)>A per-store key from the console. Publishable keys are browser-safe; secret keys are server-only.
Scope: orders:read
X-Shopper-Session<token>A 14-day shopper session from POST /v1/store/shopper/session. Preferred on a server.
cursor?stringThe nextCursor of the previous page, unchanged. A cursor that is not one we gave you is 400 invalid_parameter.
limit?integerPage size: default 50, at most 100 (more is 100; a missing or unusable value is 50).
1 <= value <= 10050The bookings.
application/json- response
data*curl -X GET 'https://api.shopeazy.co/v1/store/me/bookings' \ -H 'Authorization: Bearer sez_pub_...' \ -H 'X-Shopper-Session: <shopper_session_token>'{ "data": { "items": [], "nextCursor": null, "bookings": [], "count": 0 }}The signed-in shopper's orders at this store GET
Newest first. Only ever the caller's own orders (placed while signed in, here or on the hosted storefront). Paged: `{ items, nextCursor }`, `limit` (default 50, at most 100) and an opaque `cursor`. Old path, deprecated, sunset 1 Feb 2027: `GET /v1/me/orders`.
Apply for membership as the signed-in shopper POST
Only on a members-only store (`422 validation_error` otherwise). - **Simple stores:** JSON `{ name?, applicationNote? }`. The store's auto-approve setting applies, so the result may be `active` at once. Email and phone come from the shopper credential. - **ID-verified stores** (`store.membership.requireVerification`): `multipart/form-data` with the hosted storefront's fields and two files. A JSON body gets `422 verification_required`. A verified application is **always** `pending`. Re-applying while `pending` or `active` returns `200` with the current status and leaves the documents under review alone; a `rejected` or `revoked` shopper may re-apply with new documents. The whole request must fit the hosting body limit (about 4.5MB), so resize photos in the browser first (selfie about 1200px, ID about 1600px, JPEG). Old path, deprecated, sunset 1 Feb 2027: `POST /v1/members/apply`.