Overview
Email verification confirms that a customer owns the email address on their account. It is a two-step flow: request a verification email, then verify the token from the link.
How It Works
- Request - Send the authenticated customer a one-time verification link by email.
- Customer clicks the link - The link carries a verification token.
- Verify - Submit the token to mark the email confirmed.
Example: After signup, prompt the customer to verify their email; once they click the link, your front end posts the token to confirm it.
API Endpoints
| Method | Endpoint | Description |
|---|---|---|
GET | /api/v1/sdk/customer/email/verify | Request email verification |
POST | /api/v1/sdk/customer/email/verify | Verify email |
Important Behaviors
- Authentication: Requesting a verification email requires a bearer token; verifying the token is public (the token identifies the customer).
- Pending memberships: Verifying an email activates any memberships that were pending email confirmation.
- Already verified: Requesting verification for an already-verified email returns
404. - Throttled: Verification-email requests are rate-limited per customer.