Setup Wizard

Customer Demo setup

This page summarizes the configuration a customer app needs to use the public Lamba customer surface without relying on `platformapi` or workspace/project binding headers.

Customer auth host

https://test.id.uselamba.com

Customer API host

https://test.api.uselamba.com

Bound environment

test

1. Pick your auth mode

Embedded auth uses the customer auth API directly for password, register, magic-link, phone OTP, and email verification flows. Hosted auth uses OIDC discovery plus an Authorization Code + PKCE redirect flow.

Hosted client id: client-9a6e7dbf0e89434c82d248c31bb637d4

Hosted redirect URI: https://sandbox.demo.uselamba.com/api/auth/hosted/callback

Social and branded sign-in tests should use the hosted flow.

2. Bind workspace and project

The demo can switch into a scoped local session immediately after login or hosted callback. That replaces public `X-Tenant-Id` and `X-Project-Id` headers.

Workspace id: f9d96d5d-502b-42a6-9a10-65827960c043

Project id: f05165e2-1e21-45ac-b2e4-972dc3353d05

3. Enable admin capabilities

A project admin can use the customer admin surface for invitations, applications, domains, webhooks, roles, permissions, and deliveries.

If the active project role is not admin, the dashboard keeps those panels hidden instead of returning noisy authorization failures.

4. Wire webhook consumers

Customer webhook deliveries use the public envelope: id, type, occurredAt, workspaceId, projectId, environment, data

Delivery signatures default to v1.

Suggested sink URL: https://sandbox.webhook.demo.uselamba.com/api/webhooks/lamba

5. Verify host ownership

Customer auth lives on https://test.id.uselamba.com.

Customer runtime and admin API calls live on https://test.api.uselamba.com.

Do not route customer traffic through platformapi and do not send workspace or project binding headers on the public customer surface.

6. Smoke the end-to-end flow

1. Sign in with password, register, magic link, phone OTP, or hosted OIDC.

2. Switch into the configured workspace/project binding.

3. Verify the dashboard loads context, permissions, domains, webhooks, and admin slices from the customer API host.

7. Run the evaluation probe

Use the probe page as the manual walkthrough for auth, context, self-service, admin, and webhook scenarios.

The probe page lists the exact customer surface and local route handlers involved in each scenario.

Open the evaluation probe

8. Keep the webhook sink running

The companion WebhookSink app lets you inspect real webhook headers, payloads, signature validation, and replay protection behavior.

Suggested sink URL: https://sandbox.webhook.demo.uselamba.com/api/webhooks/lamba

Open the configured sink

Next steps