DashForDevsDocs
DocsNewsAPI v1
dashfordevs.comSign in

© 2026 DashForDevs

DocsNewsdashfordevs.comLegalStatus
DocsSite Keys & Client Sites
Introduction
Getting Started
Authentication
Products
Categories
Cart
Checkout
Blog
Reviews
Webhooks
Customers
Orders
Inventory
Shipping
Discounts
Affiliates
Email
Media & Files
Analytics & Tracking
Locations
Tax
Global Data
SEO
Error Handling
Geography
Finance
Automations
Page Types
Surveys
Billing & Subscriptions
Storefront Payments
SDK Reference
REST API
Storefront Architecture
Notifications
Security
Team & Permissions
Migrations & Import
Calendar & Appointments
Contact Forms
AI Bots
Dashboard API
Deployment
Changelog
Troubleshooting
Recipes
CLI & Deployment
Image Pipeline
White-label Platforms
Records Engine
Platform Modules
Platform Security
Site Keys & Client Sites
OverviewSite keysThe /api/site surfaceThe insights beaconCDN buildsThe powered-by badgeBuilding a paired site SDK
Use Cases
Operations

Site Keys & Client Sites

The per-site surface: dfd-site-* keys, /api/site/*, the insights beacon, CDN builds, and the paired site-SDK pattern.

  1. 01OverviewA platform runs many client sites; each gets its own narrow, revocable slice.
  2. 02Site keysIssuing, scoping, revoking — and the rules public site keys live under.
  3. 03The /api/site surfaceEvery endpoint a client site can reach, and the semantics that keep it safe.
  4. 04The insights beaconMount once, track everything, never break the site.
  5. 05CDN buildsStatic assets on the edge, with the prefix baked at build time.
  6. 06The powered-by badgeThe SDK's attribution badge, and how its referrals stay measurable.
  7. 07Building a paired site SDKThe pattern: a small branded npm package that wraps the site surface.