@spree/docs 0.1.58 → 0.1.60

package/dist/api-reference/tutorials/adyen-integration-guide-for-ios.md

@@ -163,7 +163,7 @@ Use the resultCode to inform your shopper about the current payment status.
 Possible resultCode values:
 - `authorised` - payment authorised
 - `refused` - payment refused
-- `pending` - payment pending (for payments with asynchronous flow like iDEAL). When the shopper completes the payment webhook will process process the payment.
+- `pending` - payment pending (for payments with asynchronous flow like iDEAL). When the shopper completes the payment webhook will process the payment.
 - `cancelled` - payment canceled
 - `received` - some payments needs more time to be processed. When the status is available webhook will process the payment
 - `error` - an error occurred when processing the payment. The response contains more details with the error code

package/dist/developer/core-concepts/customers.md

@@ -3,6 +3,8 @@ title: Customers
 description: Customer accounts — registration, authentication, profiles, and guest checkout
 ---
 
+import { Since } from '/snippets/since.mdx';
+
 ## Overview
 
 Customers interact with your store through the Store API. They can register, log in, manage their profile, and view order history.
@@ -168,6 +170,59 @@ curl -X PATCH 'https://api.mystore.com/api/v3/store/customer/password_resets/RES
 
 On success, the user is automatically logged in and a JWT token is returned. The reset token expires after 15 minutes (configurable via `Spree::Config.customer_password_reset_expires_in`) and is single-use (changing the password invalidates it).
 
+## Newsletter Subscriptions
+
+
+Headless storefronts often need to collect newsletter signups before account creation (footer forms, popup overlays). The Store API exposes a double opt-in subscription flow that mirrors the password reset webhook pattern.
+
+### Step 1: Subscribe
+
+
+```typescript SDK
+await client.newsletterSubscribers.create({
+  email: 'guest@example.com',
+  redirect_url: 'https://myshop.com/newsletter/confirm',
+})
+// Returns the NewsletterSubscriber (verified: false for guests)
+```
+
+```bash cURL
+curl -X POST 'https://api.mystore.com/api/v3/store/newsletter_subscribers' \
+  -H 'X-Spree-Api-Key: pk_xxx' \
+  -H 'Content-Type: application/json' \
+  -d '{
+    "email": "guest@example.com",
+    "redirect_url": "https://myshop.com/newsletter/confirm"
+  }'
+```
+
+
+The optional `redirect_url` points at the storefront page that will receive the verification token. It is validated against the store's [Allowed Origins](allowed-origins.md) — URLs that do not match are silently dropped from the webhook payload (secure-by-default).
+
+This fires a `newsletter_subscriber.subscription_requested` event whose payload includes `email`, `verification_token`, and the validated `redirect_url`. Subscribe to this event from your storefront's webhook handler to send the confirmation email — the link in the email should point to `<redirect_url>?token=<verification_token>`. The bundled `spree_emails` package also listens to this event and sends a default confirmation email if you're not running a headless storefront.
+
+If the request is authenticated via a customer JWT and the JWT's email matches the subscribed email, the subscription is **auto-verified** and no event is fired (the user has already proven email ownership).
+
+### Step 2: Verify
+
+
+```typescript SDK
+await client.newsletterSubscribers.verify({
+  token: 'token-from-email',
+})
+// Returns the verified NewsletterSubscriber
+```
+
+```bash cURL
+curl -X POST 'https://api.mystore.com/api/v3/store/newsletter_subscribers/verify' \
+  -H 'X-Spree-Api-Key: pk_xxx' \
+  -H 'Content-Type: application/json' \
+  -d '{ "token": "token-from-email" }'
+```
+
+
+On success, the subscriber is marked verified. If the subscription is linked to a customer record, that customer's `accepts_email_marketing` flag is also set to `true`. Consent is preserved across registration: if a guest subscribes and later registers with the same email, the existing subscriber is reused — registration won't accidentally reset their opt-in state.
+
 ## Customer Profile
 
 

package/dist/developer/deployment/emails.md

@@ -24,7 +24,7 @@ Spree Backend → Webhook POST → Storefront → render email → send via Rese
 
 1. **Create a webhook endpoint** in Spree Admin → Settings → Developers → Webhooks:
    - **URL:** `https://your-storefront.com/api/webhooks/spree`
-   - **Events:** `order.completed`, `order.canceled`, `order.shipped`, `customer.password_reset_requested`
+   - **Events:** `order.completed`, `order.canceled`, `order.shipped`, `customer.password_reset_requested`, `newsletter_subscriber.subscription_requested`
 
 2. **Configure the storefront** with the webhook secret and email provider:
 
@@ -45,6 +45,7 @@ EMAIL_FROM=Your Store <orders@your-domain.com>
 | `order.canceled` | Cancellation notice |
 | `order.shipped` | Shipping notification with tracking link |
 | `customer.password_reset_requested` | Password reset link |
+| `newsletter_subscriber.subscription_requested` | Newsletter double opt-in confirmation link |
 
 ### Custom Frameworks
 

package/dist/developer/storefront/nextjs/customization.md

@@ -150,6 +150,7 @@ Email templates are React components in `src/lib/emails/`:
 | `order-canceled.tsx` | `order.canceled` | Cancellation notice with items |
 | `shipment-shipped.tsx` | `order.shipped` | Tracking number and link |
 | `password-reset.tsx` | `customer.password_reset_requested` | Reset button and fallback link |
+| `newsletter-confirmation.tsx` | `newsletter_subscriber.subscription_requested` | Double opt-in confirmation link |
 
 Customize templates by editing these files directly. They use `@react-email/components` for email-safe layout primitives.
 
@@ -175,6 +176,7 @@ export const POST = createWebhookHandler({
     'order.canceled': handleOrderCanceled,
     'order.shipped': handleOrderShipped,
     'customer.password_reset_requested': handlePasswordReset,
+    'newsletter_subscriber.subscription_requested': handleNewsletterConfirmation,
   },
 })
 ```

package/dist/developer/tutorial/rich-text.md

@@ -53,7 +53,7 @@ This will render a WYSIWYG editor to the brand description field in the Admin da
 
 ## Step 3: Update permitted parameters in controller
 
-To permit the `description` attribute to be saved, we need to update the permitted parameters in the controller.   file and add the following code:
+To permit the `description` attribute to be saved, we need to update the permitted parameters in the controller file and add the following code:
 
 ```ruby app/controllers/spree/admin/brands_controller.rb {9}
 module Spree

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@spree/docs",
-  "version": "0.1.58",
+  "version": "0.1.60",
   "description": "Spree Commerce developer documentation for AI agents and local reference",
   "type": "module",
   "license": "CC-BY-4.0",