Loading…
Your Keys
Sign in on the site, then open Keys from the menu — your session carries in automatically.
Your Keys
Key access is part of the app purchase.
Your Keys
Login as a Service — one credential, every harness.
Your key is a tenant credential, not a platform setting. The store domain below is simply your tenant's identifier — the key it mints authenticates every surface you ship (Webflow exports, Next, Nuxt, Svelte, EmDash, WordPress, Drupal — and any e-commerce theme) and every agent acting under your mandates (UCP, MPP, A2A, AP2). Identity, consent, entitlements, and audit resolve in the service, not the storefront — deep commerce sync is Shopify-first, with Adobe Commerce / Magento and WooCommerce riding the same tenant model.
Step 1 — choose the store this key controls.
Not on Shopify? Use a generic identifier — your site domain, or any unique tenant name. The key binds to the identifier, not the platform — so a staging site, a POC, an application-dev environment, or a cross-channel / agent workspace can each be its own tenant with its own key.
Your Keys
Store it in a password manager now. It will never be displayed again — losing it means rotating to a new one. Paste it into the Webflow extension settings or the desktop app's key field.
Activity
Where the key goes
Webflow Designer extension → Settings → paste as the connection key. Desktop / installed app → the key field on the configure screen. Scripts → Authorization: Bearer <key>. One key per store; rotating replaces it everywhere.