GlassHouse Docs Support
Start here

API keys & authentication

Create your SuperSeeded API key, connect your store and let GlassHouse handle shopper tokens.

1. Create your API key

  1. Create an account or sign in at superseeded.ai.
  2. Open Account → API Keys and click Create API Key.
  3. Give the key a name, such as My nursery — GlassHouse. Choose an expiration if needed, then click Create.
  4. In Save your key, copy the complete key and save it securely. The full key is shown only once.

You can create your own key with a signed-in SuperSeeded account; an administrator does not need to issue it for you.

Account and billing

Creating an API key does not start a subscription. For GlassHouse subscription arrangements, contact glasshouse@superseeded.ai.

2. Connect a JavaScript store

Save the key in your backend’s environment settings. Use the store’s HTTPS origin, without a path or trailing slash.

Server environment
STORE_ORIGIN=https://store.example
GLASSHOUSE_MERCHANT_TOKEN=replace_with_your_superseeded_api_key

GLASSHOUSE_MERCHANT_TOKEN is your API key. Supply it as merchantToken to createGlassHouseHandler, as shown in the server guide. Keep it server-only; do not use a browser-exposed environment variable or pass it to mountGlassHouse.

Register the store once from server code, using the same key:

Store registration
import { registerGlassHouseStore } from '@superseeded/glasshouse/server'

await registerGlassHouseStore({
  origin: process.env.STORE_ORIGIN!,
  merchantToken: process.env.GLASSHOUSE_MERCHANT_TOKEN!,
  label: 'My nursery',
})

Restart or redeploy your backend after setting its environment. Open GlassHouse on the registered store and send a message to check the connection.

2. Connect a WooCommerce store

  1. Open WooCommerce → GlassHouse → Settings in WordPress.
  2. Paste the complete API key into Access token, without adding Bearer.
  3. Click Save access token.
  4. Check the displayed store origin, then click Register storefront.

Look for Storefront registered. Shopper chat connected. Then open GlassHouse on a product page and send a message.

The plugin stores the key on the server and manages the connection. Continue with product preparation and placement.

How shopper authentication works

CredentialPurpose
API key / merchant tokenConnects your store to your SuperSeeded account. Stored on your server or in the WooCommerce plugin settings.
Shopper tokenA short-lived token for a shopper’s GlassHouse conversation. Obtained automatically by the integration.
  1. The shopper opens GlassHouse using their existing store session.
  2. Your backend uses the merchant key and registered store origin to request a shopper token.
  3. GlassHouse uses that token for the conversation and obtains a fresh token when needed.

Shoppers do not need SuperSeeded accounts, and you do not need to create or refresh shopper tokens manually.

Guest sessions and token storage

For custom stores, implement resolveShopper using a verified store session. Create guest sessions in your store middleware and return a stable shopper ID; do not accept a shopper ID supplied in the request body.

The browser library requests tokens through /api/glasshouse/agent-session-token and holds them in memory. WooCommerce manages shopper sessions through the plugin.

Replace or revoke a key

  1. Create a replacement key in the same SuperSeeded account that registered the store.
  2. Update your server environment and redeploy, or save the replacement in WooCommerce and click Register storefront again.
  3. Send a message through GlassHouse to verify the new key.
  4. In Account → API Keys, open the old key’s action menu and choose Disable or Delete.

If a key is lost, create a replacement. If a key has been exposed, disable it immediately.

If the connection fails

Check that the key is enabled, has not expired and was copied in full. Confirm that the registered origin matches the storefront, including www if used, and that the key belongs to the account that registered it.

For custom stores, a successful /api/glasshouse/config response confirms routing only. Send a chat message to test authentication. See chat troubleshooting for session and callback checks.

Tab to a result, then press Enter to open it.