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 (a Shopify theme, the installed app or PWA, Next, Nuxt, Svelte, WordPress, Drupal, AEM, or a Webflow export) 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 what this key controls.
Brands — content keys for the Brand Studio. A brand is not a store: it carries brand:content, not configuration rights.
Any platform. A Shopify domain, the domain of a WordPress, Webflow, AEM, Next or Drupal site, or a plain name for something that is not a site at all — a POC, an application-dev environment, a cross-channel or agent workspace. The key binds to the identifier, not the platform.
The identifier becomes your tenant's name everywhere — config, embeds, and every later API call must use the same string, so it is fixed at mint time and cannot be edited afterwards. Letters, digits, hyphens and dots; start and end with a letter or digit. No https://, no trailing slash, no path, no spaces.
Your Keys
Store it in a password manager now. It will never be displayed again — losing it means rotating to a new one. Then paste it into whichever surface you are connecting: the app's configure screen, a Shopify theme block, or the key attribute on a web component.
A time-limited key stops working on its own date. Use one for a contractor, an agency engagement, or anything you would otherwise have to remember to revoke. Leave it at No expiry for a permanent integration.
Activity
Where the key goes
The key is surface-agnostic — it authenticates the tenant, not a particular editor. Paste it wherever that surface keeps its connection key: the installed app or PWA → the key field on the configure screen; a Shopify theme or app embed → the CRM Sync block's key setting; Webflow, WordPress, AEM, Next or any site → the key attribute on the CRM web components, or the extension's Settings panel where one exists. Calling the API directly → Authorization: Bearer <key>. One key per tenant; rotating replaces it everywhere.