Retail Workspace

Workspace API Keys

Create credentials for private Retail Workspace API and MCP access. Each key belongs to one workspace and only returns that workspace's data.

A workspace key is a secret

The full key is shown once. Store it in a secret manager, never commit it to source control, and rotate it immediately if it is exposed.

Create a workspace key

Sign in to Retail Workspace

Open the Retail sign-in path.

Open API Keys

In workspace settings, choose API Keys and create a new key.

Name and copy the key

Use a name that identifies the integration and environment, then copy the key before closing the dialog.

Credential scope

One workspace

The key is tied to the workspace where it was created.

Private data

Use the key for Retail API routes and the six private Retail Workspace MCP tools.

Rotatable

Replace keys without changing the workspace or its data.

Use the key

Retail API requests use X-API-Key with versioned workspace routes.

curl -H "X-API-Key: nes_your_workspace_api_key" \
  "https://api.nesika.ai/api/v1/me/products"

Retail MCP uses the same credential at https://mcp-dev.nesika.ai/workspace. ChatGPT and Claude cannot send custom headers, so with a key they use a connector URL with the key in the api_key query parameter on the backward-compatible https://mcp-dev.nesika.ai/mcp alias. Treat that URL like a password. See Retail Workspace MCP authentication.

Key safety checklist

Use a different key for local, test, and production integrations.
Keep keys in environment variables or a managed secret store.
Revoke unused keys and rotate credentials regularly.
Never place a key in client-side browser code.