@spree/docs 0.1.93 → 0.1.94

package/dist/developer/core-concepts/store-credits-gift-cards.md

@@ -83,10 +83,11 @@ Categories help organize store credits by their purpose:
 
 | Category | Description |
 |----------|-------------|
-| Default | General purpose store credit |
-| Gift Card | Store credit created from gift card redemption |
+| Default | General purpose store credit (also the default reimbursement category) |
+| Expiring | Store credit that may expire |
+| Non-expiring | Store credit that does not expire |
 
-> **INFO:** Categories can be configured as non-expiring. By default, the "Gift Card" category is non-expiring.
+> **INFO:** "Gift Card" is not a seeded category but a special name recognized by the model: any category named "Gift Card" (or one listed in `Spree::Config[:non_expiring_credit_types]`) is treated as non-expiring via `StoreCreditCategory#non_expiring?`.
 
 ### Store Credit Types
 
@@ -120,7 +121,34 @@ Store credits are managed in the Admin Panel:
 5. Enter the amount, category, and optional memo
 6. Click **Create**
 
-Store credits can also be created via the Admin API.
+Store credits can also be created via the [Admin API](../../api-reference/admin-api/introduction.md), as a nested resource under the customer:
+
+
+```typescript Admin SDK
+import { createAdminClient } from '@spree/admin-sdk'
+
+const client = createAdminClient({
+  baseUrl: 'https://store.example.com',
+  secretKey: 'sk_xxx',
+})
+
+const credit = await client.customers.storeCredits.create('cus_xxx', {
+  amount: 25.0,
+  currency: 'USD',
+  category_id: 'sccat_xxx',
+  memo: 'Goodwill credit for delayed shipment',
+})
+```
+
+```bash CLI
+spree api post /customers/cus_xxx/store_credits -d '{
+  "amount": 25.0,
+  "currency": "USD",
+  "category_id": "sccat_xxx",
+  "memo": "Goodwill credit"
+}'
+```
+
 
 ### Store Credit Events
 
@@ -151,7 +179,7 @@ erDiagram
         decimal amount_used
         decimal amount_authorized
         string currency
-        datetime expires_at
+        date expires_at
         datetime redeemed_at
     }
 
@@ -160,7 +188,7 @@ erDiagram
         integer codes_count
         decimal amount
         string currency
-        datetime expires_at
+        date expires_at
     }
 ```
 
@@ -218,7 +246,34 @@ flowchart TB
 4. Click **Create**
 5. Share the generated code with the recipient
 
-Gift cards can also be created via the Admin API.
+Gift cards can also be created via the [Admin API](../../api-reference/admin-api/introduction.md). The code is generated automatically if you don't supply one:
+
+
+```typescript Admin SDK
+import { createAdminClient } from '@spree/admin-sdk'
+
+const client = createAdminClient({
+  baseUrl: 'https://store.example.com',
+  secretKey: 'sk_xxx',
+})
+
+const giftCard = await client.giftCards.create({
+  amount: 50,
+  currency: 'USD',
+  expires_at: '2026-12-31',
+})
+
+console.log(giftCard.code) // share this with the recipient
+```
+
+```bash CLI
+spree api post /gift_cards -d '{
+  "amount": 50,
+  "currency": "USD",
+  "expires_at": "2026-12-31"
+}'
+```
+
 
 #### Batch Gift Card Generation
 
@@ -233,6 +288,30 @@ For promotions or bulk distribution, you can create multiple gift cards at once
    - **Expiration** - Optional expiration date
 4. Click **Create**
 
+Batches can also be created via the Admin API:
+
+
+```typescript Admin SDK
+const batch = await client.giftCardBatches.create({
+  prefix: 'HOLIDAY',
+  codes_count: 1000,
+  amount: 25,
+  currency: 'USD',
+  expires_at: '2026-12-31',
+})
+```
+
+```bash CLI
+spree api post /gift_card_batches -d '{
+  "prefix": "HOLIDAY",
+  "codes_count": 1000,
+  "amount": 25,
+  "currency": "USD",
+  "expires_at": "2026-12-31"
+}'
+```
+
+
 > **INFO:** Large batches are processed in the background to avoid timeout issues.
 
 ### Redeeming Gift Cards
@@ -246,10 +325,10 @@ When a gift card is applied to an order:
 - The gift card is marked as redeemed (or partially redeemed)
 - No Store Credit is created for guest checkouts
 
-Gift cards are applied using the same coupon codes endpoint as promotion codes. The endpoint automatically detects whether the code is a promotion coupon or a gift card.
+Gift cards are applied via a dedicated `POST /api/v3/store/carts/:cart_id/gift_cards` endpoint (separate from the `discount_codes` endpoint used for promotion codes); the discount-codes endpoint does not handle gift cards. See the [cart & checkout SDK guide](../sdk/store/cart-checkout.md) for the full cart flow these calls belong to.
 
 
-```typescript SDK
+```typescript Store SDK
 // Apply gift card code to cart (works for guests and registered customers)
 // Gift cards use a dedicated endpoint — they reduce amount_due, not total
 const cart = await client.carts.giftCards.apply('cart_abc123', 'abc1234def', {
@@ -324,3 +403,5 @@ When a registered customer has multiple store credits, they are applied in order
 - [Orders](orders.md) — Order management
 - [Customers](customers.md) — Customer management
 - [Events](events.md) — Event system and subscribers
+- [Admin SDK Quickstart](../sdk/admin/quickstart.md) — Set up and authenticate the Admin SDK
+- [Monetary Amounts](../../api-reference/store-api/monetary-amounts.md) — How the API represents `amount`, `amount_used`, and other money fields

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

@@ -1,11 +1,11 @@
 ---
 title: Stores
-description: The Store is Spree's top-level multi-tenant boundary — learn how products, orders, channels, markets, and stock locations are scoped to a store.
+description: The Store is Spree's top-level multi-tenant boundary — learn how products, orders, channels, and markets are scoped to a store.
 ---
 
 ## Overview
 
-The Store is the top-level tenant in Spree. Every resource — products, orders, channels, markets, taxonomies, stock locations — belongs to exactly one store. A store owns its branding (logo, custom domain, mail-from address), its [channels](channels.md) (online, POS, wholesale, …), its [markets](markets.md) (region/currency/locale), and its catalog.
+The Store is the top-level tenant in Spree. Every resource — products, orders, channels, markets, taxonomies — belongs to exactly one store. A store owns its branding (logo, custom domain, mail-from address), its [channels](channels.md) (online, POS, wholesale, …), its [markets](markets.md) (region/currency/locale), and its catalog.
 
 ## Store Attributes
 
@@ -19,33 +19,34 @@ The Store is the top-level tenant in Spree. Every resource — products, orders,
 | `seo_title` | Custom SEO title |
 | `customer_support_email` | Email for customer support inquiries |
 | `mail_from_address` | Sender address for transactional emails |
-| `logo_image_url` | URL to the store's logo |
+| `logo_url` | URL to the store's logo |
 | `facebook`, `twitter`, `instagram` | Social media links |
-| `payment_methods` | Payment methods available in this store |
 
 ## Fetching Store Information
 
-Use the store endpoint to get the current store's configuration — useful for rendering logos, SEO metadata, and footer content:
+Store configuration is exposed through the Admin API. Use the store endpoint to read the current store's settings — name, URL, branding, and email addresses:
 
 
-```typescript SDK
-const store = await client.store.get()
+```typescript Admin SDK
+const store = await adminClient.store.get()
 // {
 //   name: "My Store",
 //   url: "https://mystore.com",
-//   logo_image_url: "https://cdn.mystore.com/logo.png",
+//   logo_url: "https://cdn.mystore.com/logo.png",
+//   mailer_logo_url: "https://cdn.mystore.com/mailer-logo.png",
 //   customer_support_email: "support@mystore.com",
-//   payment_methods: [{ id: "pm_xxx", name: "Stripe", kind: "card" }],
 //   ...
 // }
 ```
 
 ```bash cURL
-curl 'https://api.mystore.com/api/v3/store/store' \
-  -H 'X-Spree-API-Key: pk_xxx'
+curl 'https://api.mystore.com/api/v3/admin/store' \
+  -H 'X-Spree-API-Key: sk_xxx'
 ```
 
 
+This is an admin endpoint, so it requires a secret API key (`sk_xxx`) or a Bearer JWT — a publishable key cannot reach it.
+
 ## Channels vs. Markets
 
 Two different ways to split a store, often confused:
@@ -65,7 +66,7 @@ Each store owns its own resources. Products, orders, channels, markets, and taxo
 | [**Markets**](markets.md) | A store has many markets, each defining a geographic region with its own currency and locale |
 | [**Orders**](orders.md) | An order belongs to one store and one channel |
 | [**Products**](products.md) | A product belongs to one store. Its visibility across channels is controlled by [publications](channels.md#publishing-products-on-channels). |
-| [**Taxonomies**](products.md#taxons-and-taxonomies) | A taxonomy belongs to one store |
+| [**Taxonomies**](products.md#categories) | A taxonomy belongs to one store |
 | [**Payment Methods**](payments.md) | A payment method belongs to one store |
 | [**Shipping Methods**](shipments.md) | A shipping method belongs to one store |
 | [**Promotions**](promotions.md) | A promotion belongs to one store |
@@ -75,9 +76,9 @@ Each store owns its own resources. Products, orders, channels, markets, and taxo
 If you need one Spree backend to serve **multiple distinct merchant brands** — different domains, different catalogs, different admin teams — there are two patterns:
 
 - **Multiple channels under one store** (recommended for most cases) — model each storefront as a Sales Channel. Products are scoped per-channel via publications, orders carry the channel that originated them, and routing/pricing can differ per channel. This is the supported pattern in core Spree 5.5+.
-- **Multiple stores in one app** — the legacy multi-store pattern, where each store is fully independent (catalog, admin, branding). In Spree 5.5+ this requires the `spree_multi_store` extension. Core Spree treats each product as belonging to a single store.
+- **Multiple stores in one app** — the legacy multi-store pattern, where each store is fully independent (catalog, admin, branding). In Spree 5.5+ this requires the [spree_multi_store](../multi-store/quickstart.md) extension. Core Spree treats each product as belonging to a single store.
 
-For most multi-brand operations, the channel pattern is simpler and more flexible. Reach for `spree_multi_store` only when stores need genuinely independent catalogs, branding, and admin teams.
+For most multi-brand operations, the channel pattern is simpler and more flexible. Reach for [spree_multi_store](../multi-store/quickstart.md) only when stores need genuinely independent catalogs, branding, and admin teams.
 
 ## Related Documentation
 
@@ -85,3 +86,4 @@ For most multi-brand operations, the channel pattern is simpler and more flexibl
 - [Markets](markets.md) — Multi-region commerce within a store
 - [Products](products.md) — Product catalog
 - [Orders](orders.md) — Order management and checkout
+- [Admin SDK](../sdk/admin/quickstart.md) — TypeScript client for the Admin API used to read and update store configuration

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

@@ -55,6 +55,33 @@ Each product is assigned a tax category. One category can be set as the default
 | `is_default` | Whether this is the default category | `true` |
 | `tax_code` | Code from your tax provider (e.g., Stripe, Avalara) | `1257L` |
 
+Manage tax categories via the [Admin API](../../api-reference/admin-api/introduction.md), using the [Admin SDK resource clients](../sdk/admin/resources.md):
+
+
+```typescript Admin SDK
+import { createAdminClient } from '@spree/admin-sdk'
+
+const client = createAdminClient({
+  baseUrl: 'https://store.example.com',
+  secretKey: 'sk_xxx',
+})
+
+const clothing = await client.taxCategories.create({
+  name: 'Clothing',
+  tax_code: '1257L',
+  is_default: true,
+})
+
+await client.taxCategories.update('taxcat_xxx', { is_default: false })
+await client.taxCategories.delete('taxcat_xxx')
+```
+
+```bash CLI
+spree api post /tax_categories -d '{"name": "Clothing", "tax_code": "1257L", "is_default": true}'
+spree api get /tax_categories
+```
+
+
 ## Tax Rates
 
 Tax rates define the percentage charged for a specific tax category within a geographic zone.
@@ -133,3 +160,4 @@ Tax categories and rates are managed in the Admin Panel under **Settings → Tax
 - [Addresses](addresses.md) — Zones and address-based taxation
 - [Adjustments](adjustments.md) — Tax adjustments
 - [Orders](orders.md) — How taxes affect order totals
+- [Avalara integration](../../integrations/tax/avalara.md) — Automated tax calculation for complex jurisdictions

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

@@ -52,23 +52,23 @@ erDiagram
 
 | Resource         | Translatable Fields                                                                                                                                                                 |
 | ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Product          | `name`, `description`, `slug`, `meta_description`, `meta_keywords`, `meta_title`                                                                                                             |
+| Product          | `name`, `description`, `slug`, `meta_description`, `meta_title`                                                                                                             |
 | Taxon            | `name`, `description`, `permalink`                                                                                                                                                        |
 | Taxonomy         | `name`                                                                                                                                                                                |
 | Option Type      | `presentation`                                                                                                                                                                  |
 | Option Value     | `presentation`                                                                                                                                                                  |
 | Property         | `presentation`                                                                                                                                                   |
 | Product Property | `value`                                                                                                                                                                 |
-| Store            | `name`, `meta_description`, `meta_keywords`, `seo_title`, `facebook`, `twitter`, `instagram`, `customer_support_email`, `description`, `address`, `contact_phone` |
+| Store            | `name`, `meta_description`, `meta_keywords`, `seo_title`, `customer_support_email`, `address`, `contact_phone` |
 
 ### Store API
 
-To retrieve translated content, pass the locale via the `X-Spree-Locale` header or the SDK `locale` option:
+To retrieve translated content, pass the locale via the [`X-Spree-Locale` header](../../api-reference/store-api/localization.md) or the SDK `locale` option:
 
 
-```typescript SDK
+```typescript Store SDK
 // Fetch product in French
-const product = await client.products.get('spree-tote', {
+const product = await client.products.get('spree-tote', {}, {
   locale: 'fr',
 })
 
@@ -82,6 +82,14 @@ const { data: categories } = await client.categories.list({}, {
 })
 ```
 
+```typescript Admin SDK
+// Pass the locale as a request option to get translated content.
+// The Admin API resolves by prefixed ID only — slugs are not accepted.
+const product = await adminClient.products.get('prod_86Rf07xd4z', {}, { locale: 'fr' })
+
+const { data: categories } = await adminClient.categories.list({}, { locale: 'de' })
+```
+
 ```bash cURL
 # Fetch product in French
 curl 'https://api.mystore.com/api/v3/store/products/spree-tote' \
@@ -96,11 +104,11 @@ Slugs are also localized — a product can have different slugs per locale. See
 
 Translations are managed in the Admin Panel. When editing a product, taxon, or other translatable resource, switch the locale selector to enter content in each language.
 
-Translations can also be managed via the Admin API.
+Translations can also be [managed via the Admin API](../sdk/admin/quickstart.md).
 
 ## UI Translations
 
-Spree stores UI translation strings in a separate project: [Spree I18n](https://github.com/spree/spree_i18n). This is a community-maintained project with locale files for 43+ languages.
+Spree stores UI translation strings in a separate project: [Spree I18n](https://github.com/spree-contrib/spree_i18n). This is a community-maintained project with locale files for 43+ languages.
 
 To install UI translations:
 
@@ -121,6 +129,7 @@ Once installed, all translation files are available automatically — no need to
 ## Related Documentation
 
 - [Markets](markets.md) — Locale and currency configuration per geographic region
+- [Localization](../../api-reference/store-api/localization.md) — Locale, currency, and country headers in API requests
 - [Slugs](slugs.md) — Localized slugs and URL identifiers
 - [Stores](stores.md) — Multi-store setup
 - [Products](products.md) — Product translations

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

@@ -57,7 +57,7 @@ erDiagram
 ### Registration
 
 
-```typescript SDK
+```typescript Store SDK
 const { token, user } = await client.customers.create({
   email: 'john@example.com',
   password: 'password123',
@@ -86,7 +86,7 @@ curl -X POST 'https://api.mystore.com/api/v3/store/customers' \
 ### Login
 
 
-```typescript SDK
+```typescript Store SDK
 const { token, user } = await client.auth.login({
   email: 'john@example.com',
   password: 'password123',
@@ -105,29 +105,31 @@ curl -X POST 'https://api.mystore.com/api/v3/store/auth/login' \
 ```
 
 
-The response includes a JWT `token` and a `user` object. Pass the token in subsequent requests via the `Authorization: Bearer <token>` header.
+The response includes a [JWT token](../../api-reference/store-api/authentication.md) and a `user` object. Pass the token in subsequent requests via the `Authorization: Bearer <token>` header. See the [account SDK guide](../sdk/store/account.md) for the full `auth.login`, refresh, and profile flows.
 
 ### Token Refresh
 
 Refresh an expiring token to keep the session alive:
 
 
-```typescript SDK
+```typescript Store SDK
 const { token } = await client.auth.refresh({
-  token: existingToken,
+  refresh_token: existingRefreshToken,
 })
 ```
 
 ```bash cURL
 curl -X POST 'https://api.mystore.com/api/v3/store/auth/refresh' \
-  -H 'Authorization: Bearer <jwt_token>'
+  -H 'X-Spree-API-Key: pk_xxx' \
+  -H 'Content-Type: application/json' \
+  -d '{ "refresh_token": "rt_xxx" }'
 ```
 
 
 ### Customer Profile
 
 
-```typescript SDK
+```typescript Store SDK
 // Get current customer
 const customer = await client.customer.get()
 // {
@@ -149,11 +151,11 @@ const updated = await client.customer.update({
 
 ```bash cURL
 # Get current customer
-curl 'https://api.mystore.com/api/v3/store/customer' \
+curl 'https://api.mystore.com/api/v3/store/customers/me' \
   -H 'Authorization: Bearer <jwt_token>'
 
 # Update profile
-curl -X PATCH 'https://api.mystore.com/api/v3/store/customer' \
+curl -X PATCH 'https://api.mystore.com/api/v3/store/customers/me' \
   -H 'Authorization: Bearer <jwt_token>' \
   -H 'Content-Type: application/json' \
   -d '{ "first_name": "Jonathan", "accepts_email_marketing": true }'
@@ -297,3 +299,5 @@ See the [Customize Permissions guide](../customization/permissions.md) for detai
 - [Authentication](../customization/authentication.md) — Custom authentication setup
 - [Permissions](../customization/permissions.md) — Roles and authorization
 - [Events](events.md) — Subscribe to user and invitation events
+- [Store API Authentication](../../api-reference/store-api/authentication.md) — Customer JWT auth flow
+- [Admin API Authentication](../../api-reference/admin-api/authentication.md) — Staff JWT + scopes auth flow

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

@@ -56,20 +56,39 @@ flowchart LR
 
 Navigate to **Settings → Developers → Webhooks** in the admin panel to create and manage webhook endpoints.
 
-### Via Code
+### Via the Admin API
 
-```ruby
-endpoint = Spree::WebhookEndpoint.create!(
-  store: Spree::Store.default,
+
+```typescript Admin SDK
+import { createAdminClient } from '@spree/admin-sdk'
+
+const client = createAdminClient({
+  baseUrl: 'https://store.example.com',
+  secretKey: 'sk_xxx',
+})
+
+const endpoint = await client.webhookEndpoints.create({
   url: 'https://example.com/webhooks/spree',
   subscriptions: ['order.*', 'product.created'],
-  active: true
-)
+  active: true,
+})
+
+// secret_key is auto-generated and returned ONLY on create —
+// store it now for HMAC signature verification.
+endpoint.secret_key // => "a1b2c3d4e5f6..." (64-character hex string)
+```
 
-# The secret_key is auto-generated
-endpoint.secret_key # => "a1b2c3d4e5f6..." (64-character hex string)
+```bash CLI
+spree api post /webhook_endpoints -d '{
+  "url": "https://example.com/webhooks/spree",
+  "subscriptions": ["order.*", "product.created"],
+  "active": true
+}'
 ```
 
+
+> **WARNING:** The `secret_key` is returned **only once**, in the create response. Save it immediately — it can't be retrieved later and is required to verify webhook signatures.
+
 ### Endpoint Attributes
 
 | Attribute | Type | Description |
@@ -78,41 +97,35 @@ endpoint.secret_key # => "a1b2c3d4e5f6..." (64-character hex string)
 | `active` | Boolean | Enable/disable delivery to this endpoint |
 | `subscriptions` | Array | Event patterns to subscribe to |
 | `secret_key` | String | Auto-generated key for HMAC signature verification |
-| `store_id` | Integer | The store this endpoint belongs to |
+
+Endpoints always belong to the current store — the association is set automatically from the request scope, so you never pass it when creating or updating an endpoint.
 
 ## Event Subscriptions
 
-The `subscriptions` attribute controls which events trigger webhooks to this endpoint.
+The `subscriptions` attribute controls which events trigger webhooks to this endpoint. Set it when creating the endpoint, or change it later:
 
-### Subscribe to Specific Events
 
-```ruby
-endpoint.subscriptions = ['order.completed', 'order.canceled']
+```typescript Admin SDK
+await client.webhookEndpoints.update('whe_xxx', {
+  subscriptions: ['order.completed', 'order.canceled'],
+})
 ```
 
-### Subscribe to Event Patterns
-
-Use wildcards to subscribe to multiple related events:
-
-```ruby
-# All order events
-endpoint.subscriptions = ['order.*']
-
-# All creation events
-endpoint.subscriptions = ['*.created']
-
-# Multiple patterns
-endpoint.subscriptions = ['order.*', 'payment.*', 'shipment.shipped']
+```bash CLI
+spree api patch /webhook_endpoints/whe_xxx \
+  -d '{"subscriptions": ["order.completed", "order.canceled"]}'
 ```
 
-### Subscribe to All Events
 
-Leave subscriptions empty or use `*` to receive all events:
+The `subscriptions` array accepts exact event names and wildcard patterns:
 
-```ruby
-endpoint.subscriptions = []    # All events
-endpoint.subscriptions = ['*'] # All events (explicit)
-```
+| `subscriptions` value | Receives |
+|---|---|
+| `['order.completed', 'order.canceled']` | Only those two events |
+| `['order.*']` | All order events |
+| `['*.created']` | All creation events |
+| `['order.*', 'payment.*', 'shipment.shipped']` | Multiple patterns |
+| `[]` or `['*']` | All events |
 
 ## Webhook Payload
 
@@ -126,10 +139,11 @@ Each webhook delivery sends a JSON payload with the following structure. The `da
   "data": {
     "id": "or_m3Rp9wXz",
     "number": "R123456789",
-    "state": "complete",
+    "fulfillment_status": "shipped",
+    "payment_status": "paid",
     "total": "99.99",
     "display_total": "$99.99",
-    "item_count": 3,
+    "total_quantity": 3,
     "currency": "USD",
     "items": [ ... ],
     "fulfillments": [ ... ],
@@ -163,6 +177,7 @@ Each webhook request includes these headers:
 | `User-Agent` | `Spree-Webhooks/1.0` |
 | `X-Spree-Webhook-Event` | Event name (e.g., `order.completed`) |
 | `X-Spree-Webhook-Signature` | HMAC-SHA256 signature for verification |
+| `X-Spree-Webhook-Timestamp` | Unix timestamp (seconds) generated at send time; included in the HMAC-SHA256 signed string as `{timestamp}.{payload}` and required to verify `X-Spree-Webhook-Signature` |
 
 ### Verifying Webhook Signatures
 
@@ -244,21 +259,23 @@ Failed webhook deliveries automatically retry up to 5 times with exponential bac
 
 ### Checking Delivery Status
 
-```ruby
-endpoint = Spree::WebhookEndpoint.find(id)
+Inspect an endpoint's delivery log, and re-send a failed delivery, via the Admin API:
 
-# Recent deliveries
-endpoint.webhook_deliveries.recent
 
-# Filter by status
-endpoint.webhook_deliveries.successful
-endpoint.webhook_deliveries.failed
-endpoint.webhook_deliveries.pending
+```typescript Admin SDK
+// Recent deliveries for an endpoint
+const { data: deliveries } = await client.webhookEndpoints.deliveries.list('whe_xxx')
+
+// Re-send a specific delivery
+await client.webhookEndpoints.deliveries.redeliver('whe_xxx', 'whd_xxx')
+```
 
-# Filter by event
-endpoint.webhook_deliveries.for_event('order.completed')
+```bash CLI
+spree api get /webhook_endpoints/whe_xxx/deliveries -q event_name_eq=order.completed
+spree api post /webhook_endpoints/whe_xxx/deliveries/whd_xxx/redeliver
 ```
 
+
 ### Delivery Attributes
 
 | Attribute | Description |
@@ -309,31 +326,38 @@ Common webhook events include:
 | `payment.paid` | Payment was completed |
 | `product.created` | New product created |
 | `product.updated` | Product was modified |
-| `customer.created` | New customer registered |
+| `user.created` | New customer/user registered (the admin user class emits `admin.created`) |
 
 ## Testing Webhooks
 
 ### In Development
 
-Use tools like [ngrok](https://ngrok.com) or [webhook.site](https://webhook.site) to test webhooks locally:
+Use tools like [ngrok](https://ngrok.com) or [webhook.site](https://webhook.site) to test webhooks locally. Create a test endpoint pointed at the tunnel:
 
-```ruby
-# Create a test endpoint
-endpoint = Spree::WebhookEndpoint.create!(
-  store: Spree::Store.default,
+
+```typescript Admin SDK
+const endpoint = await client.webhookEndpoints.create({
   url: 'https://your-ngrok-url.ngrok.io/webhooks',
   subscriptions: ['order.*'],
-  active: true
-)
+  active: true,
+})
 
-# Trigger an event
-order = Spree::Order.complete.last
-order.publish_event('order.completed')
+// Fire a synthetic delivery to confirm it's reachable
+await client.webhookEndpoints.sendTest(endpoint.id)
+```
 
-# Check delivery
-endpoint.webhook_deliveries.last.success?
+```bash CLI
+spree api post /webhook_endpoints -d '{
+  "url": "https://your-ngrok-url.ngrok.io/webhooks",
+  "subscriptions": ["order.*"],
+  "active": true
+}'
+spree api post /webhook_endpoints/whe_xxx/send_test
 ```
 
+
+`send_test` delivers a synthetic `webhook.test` event so you can verify the endpoint is reachable and your signature-verification code works, without having to trigger a real order.
+
 ### In Tests
 
 ```ruby
@@ -381,18 +405,25 @@ end
 
 ### Deliveries Failing
 
-Check the delivery record for details:
+Check the delivery records for details — each carries `error_type`, `request_errors`, `response_code`, and `response_body`. Filter the log with [Ransack predicates](../../api-reference/admin-api/querying.md) such as `success_eq=false` or `event_name_eq`:
 
-```ruby
-delivery = endpoint.webhook_deliveries.failed.last
-delivery.error_type      # => 'timeout' or 'connection_error'
-delivery.request_errors  # => Error message
-delivery.response_code   # => HTTP status code
-delivery.response_body   # => Response from your endpoint
+
+```typescript Admin SDK
+const { data: deliveries } = await client.webhookEndpoints.deliveries.list('whe_xxx', {
+  success_eq: false,
+})
+const failed = deliveries[0]
+// failed.error_type, failed.request_errors, failed.response_code, failed.response_body
+```
+
+```bash CLI
+spree api get /webhook_endpoints/whe_xxx/deliveries -q success_eq=false
 ```
 
+
 ## Related Documentation
 
 - [Events](events.md) - Understanding Spree's event system
+- [Admin SDK](../sdk/admin/quickstart.md) - Setting up the `@spree/admin-sdk` client used in the management examples above
 - [Customization Quickstart](../customization/quickstart.md) - Overview of all customization options
 - [Dependencies](../customization/dependencies.md) - Customizing Spree services