Archive a customer (soft delete)
- Credentials
- OAuth access token
- Scopes
customers:write- Subscription
- Needs an active plan. Otherwise
403 subscription_locked. - Idempotency
- Send an
Idempotency-Keyheader. A retry with the same key does the work once.
Access: OAuth scope customers:write; write-gated by the subscription.
merchantOAuth customers:writeAuthorizationBearer <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: customers:write
storeId*stringA store the person can reach. Any other id answers 404, never 403.
customerId*stringIdempotency-Key*stringRequired on every write. Minted on the device when the person taps, reused on every retry. A write without one, or with one that does not match the pattern, is refused with 422 validation_error. Scoped to the token's subject, remembered 24 hours. A replay returns the first 2xx response with Idempotent-Replay: true; a request still running answers 409 in_flight; the same key with a different method, path or body answers 409 idempotency_key_reused; non-2xx results are not remembered. If the key store cannot be read nothing is processed and the answer is 503 idempotency_unavailable: retry with the same key.
^[A-Za-z0-9_-]{8,128}$OK
application/json- response
data*curl -X DELETE 'https://api.shopeazy.co/v1/merchant/stores/<storeId>/customers/<customerId>' \ -H 'Authorization: Bearer <access_token>' \ -H 'Idempotency-Key: <unique_key>'{ "data": { "id": "hqq5kNvq3gO6U79EGMmX", "status": "archived" }}Edit a customer PATCH
Access: OAuth scope `customers:write`; write-gated by the subscription.
Restore an archived customer POST
Puts an archived customer (`archiveCustomer`) back on the customer list as active, with their history. Restoring a customer who is already active is a no-op that answers the same way, so a retry is always safe. Access: OAuth scope `customers:write`; write-gated by the subscription.