ShopEazydevelopers
API referenceStorefront APIMember review

One member, with KYC details and short-lived document URLs

Credentials
  • Store key
Scopes
members:manage
Key type
Secret store key only. Keep it on your server.
GET
/v1/store/members/{uid}

Old path, deprecated, sunset 1 Feb 2027: GET /v1/members/{uid}.

Authorization

storeKey members:manage
headerAuthorizationBearer <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: members:manage

Path Parameters

uid*string

The shopper's user id within the store's tenant.

Response Body

The member.

application/json
  1. response
data*
Example Request
curl -X GET 'https://api.shopeazy.co/v1/store/members/<uid>' \  -H 'Authorization: Bearer sez_sk_...'
Example Response
{  "data": {    "uid": "N5QACKmZ7d37y4LqAkQzUrk1Fci0",    "status": "pending",    "name": "Thandi Mokoena",    "email": "thandi.mokoena@example.com",    "phone": null,    "applicationNote": "I run a plant swap in Greenside and would love member prices.",    "appliedAt": 1792924403819,    "decidedAt": null,    "decisionNote": null,    "verification": null  }}

List the store's members GET

Secret key only. Rows carry no signed document URLs; fetch one member for those. Paged: `{ items, nextCursor }`, `limit` (default 50, at most 100) and an opaque `cursor`. Old path, deprecated, sunset 1 Feb 2027: `GET /v1/members`.

Approve a membership POST

Idempotent. `note` becomes the member's `decisionNote`, which the shopper sees on `GET /v1/store/me`. Old path, deprecated, sunset 1 Feb 2027: `POST /v1/members/{uid}/approve`.