Authentication
API keys, OAuth 2.1, and workspace scoping
Authentication
The Lexsis Storefront API supports two authentication methods.
API Keys
API keys use the lx_ prefix and are scoped to your organization.
Each key has:
- Tenant scope — tied to one brand/organization
- Workspace — default workspace for API calls
- Permissions —
read,write, oradmin
Creating a Key
Navigate to Settings → API Keys → Create in your Lexsis dashboard.
Using a Key
Pass your API key in the X-API-Key header:
X-API-Key: lx_your_key_hereOAuth 2.1
The platform implements RFC 9728 (OAuth Protected Resource Metadata) for programmatic access.
Well-known Endpoints
| Endpoint | Purpose |
|---|---|
/.well-known/oauth-protected-resource | Resource metadata |
/.well-known/oauth-authorization-server | Authorization server metadata |
Flow
- Client discovers auth requirements via protected resource metadata
- Client authenticates via authorization server
- Bearer token issued for subsequent API calls
- Scopes:
mcp:tools
Workspace Scoping
API calls are scoped to a workspace. The workspace resolves from:
X-Workspace-Idheader — optional override (must belong to same tenant)- API key default — the workspace set when the key was created
To override the default workspace for a specific request:
X-Workspace-Id: ws_your_workspace_idConnection Methods
| Method | Transport |
|---|---|
| Claude Code | stdio (local process) |
| Claude Desktop | stdio via config |
| HTTP clients | POST https://mcp.trylexsis.com/mcp with Bearer token |
| ChatGPT | OpenAPI schema at /openapi.json |
Permissions
| Level | Can do |
|---|---|
read | List and get resources (blueprints, pages, analytics) |
write | Create/modify pages, blueprints, experiments |
admin | Manage API keys, workspace settings, domain routes |