ShopEazydevelopers
API referenceMerchant API BetaMembers

One application or member

Beta
Credentials
  • OAuth access token
Scopes
settings:write
Role
Owners and admins only. Staff get 403 forbidden.
GET
/v1/merchant/stores/{storeId}/members/{memberId}

The selfie and ID stay in the console: only whether they were sent is shown.

Access: OAuth scope settings:write; owner/admin only; not write-gated.

Authorization

merchantOAuth settings:write
headerAuthorizationBearer <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: settings:write

Path Parameters

storeId*string

A store the person can reach. Any other id answers 404, never 403.

memberId*string

A member's id (the shopper's uid), from GET /members.

Response Body

OK

application/json
  1. response
data*

A member as the shop sees it. note is the applicant's own words (untrusted text). The selfie and ID are never returned.

Example Request
curl -X GET 'https://api.shopeazy.co/v1/merchant/stores/<storeId>/members/<memberId>' \  -H 'Authorization: Bearer <access_token>'
Example Response
{  "data": {    "id": "string",    "name": "string",    "email": "string",    "phone": "string",    "status": "pending",    "note": "string",    "hasIdCheck": true,    "appliedAt": 0,    "decidedAt": 0  }}

Membership requests, or members by status GET

For members-only shops. At most 100 are returned; `total` counts them all. ID documents are never shown. Access: OAuth scope `settings:write`; owner/admin only; not write-gated. Paged: `{ items, nextCursor }`, `limit` (default 50, at most 100) and an opaque `cursor`.

Let a pending applicant in POST

The applicant is emailed a welcome. Approving someone already in changes nothing. A connected AI app cannot approve an applicant who sent a selfie and ID (403 `forbidden`): a person looks at the documents in the console. The ShopEazy app can. Access: OAuth scope `settings:write`; owner/admin only; write-gated by the subscription.