Skip to main content
Remove a recipient from a store’s recipient list. The address can be added again later.
Authentication: API Key (owner or admin role required)

Request Body

Example Request

Success Response (200)

Removing the last recipient returns 200 — there is no “keep at least one” guard. The store then falls back to the owner’s account email, using the store-level notify* toggles. The fallback entry itself cannot be removed: it is not a stored row, so sending its OWNER_<storeId> sentinel id returns 404. To replace it, add a real recipient. Consumer-facing transactional email is a separate pipeline and keeps working.

Response Fields

Errors

Retry policy: Never retry 4xx — fix the request and resubmit. Retry 5xx with exponential backoff (start 5s, max 3 attempts).