Welcome to Lamba Docs
Choose an integration path, get the right console credentials, and wire Lamba customer identity, Customer API calls, and webhook-ready workflows into your product.
Choose your integration path
Start from the surface you are wiring. Each guide shows where to get credentials, which host to call, request and response fields, and the first check that proves the integration works.
| Path | Use when | Start here | Credentials needed | First success check |
|---|---|---|---|---|
| Next.js embedded auth | You own the login UI and want route handlers, HttpOnly cookies, and server-side Customer API reads. | Next.js integration | Workspace, Project, environment, optional App Client | A protected page renders `/v1/me/context` for a signed-in user. |
| Hosted Auth / OIDC | You want Lamba to own the sign-in surface or need standards-based OIDC integration. | Hosted auth | App Client ID, redirect URI, optional confidential secret | `/connect/token` returns tokens and your callback validates state and nonce. |
| Customer API | Your backend needs profile, membership, authorization, admin, domain, webhook, or SMS add-on operations. | Customer API contract | Customer session token or Management client credentials | `GET /v1/me/context` or an allowed `/v1/admin/*` route returns JSON. |
| Webhooks | You need signed lifecycle events, delivery retries, and downstream processing. | Webhooks integration | Webhook endpoint URL, subscribed events, signing secret | A sandbox delivery verifies its signature and is deduplicated by event ID. |
| Domains, social, and growth | You have the auth path working and now need branded hosts, social login, or preview growth workflows. | Next integration step | Domain ownership, provider credentials, Project/environment selection | The console shows verified/bound setup and public events use the same Project context. |
Start hereIntegration guidesAdd Lamba to a Next.js app with customer auth credentials, HttpOnly cookies, request fields, response fields, and scoped Customer API reads.Open integration guideBuildCustomer APIStart Customer API integration with console credentials, token-scoped requests, management client credentials, request fields, response fields, and public endpoint coverage.Open customer API contractOperateWebhooks & eventsRegister Lamba webhook endpoints from Console, get the signing secret, verify delivery headers, understand payload fields, and process retries safely.Open webhook docsModelWorkspace & Project modelUnderstand how Lamba models workspaces, projects, and their runtime boundaries.Open model guideGrowGrowth workflowsConnect account, membership, session, project, campaign, loyalty, and lifecycle signals without splitting identity context.Open growth guide
Explore by feature
Follow the docs by the runtime capability you are integrating, not by internal storage names.
AuthenticationHosted sign-in, OIDC discovery, PKCE, social provider setup, and customer session exchange.Hosted authHosted login, registration, refresh, logout, branding, and redirect handling for customer-facing products.Project rolesSeparate Team Member console access from Project Member runtime permissions.Member lifecycleKeep Team Member console access separate from Project Member runtime access across invites, join, and register flows.SessionsKeep scoped runtime sessions explicit across workspace, project, and environment boundaries.WebhooksRegister endpoints, verify signatures, handle retries, and process immutable event facts.Custom domainsBind branded auth and API hosts while preserving issuer and environment separation.Growth workflowsConnect identity, membership, session, campaign, loyalty, and lifecycle signals without splitting context.CampaignsPlan campaign audiences, delivery signals, email/SMS capacity, and plan-aware limits from one identity model.LoyaltyTie earn, spend, reversal, and retention activity to identity-linked loyalty context.AnalyticsTrack MAU, auth success, sessions, campaign delivery, loyalty activity, exports, and retention limits.
Explore by integration
These pages combine setup steps with public request and response contracts, so setup steps and field-level details live together.
Next.jsAdd Lamba to App Router with server helpers, auth callback handling, protected pages, and logout.OIDC and OAuth2Use discovery, Authorization Code + PKCE, exact redirect URIs, token validation, and JWKS caching.Customer APICall public customer auth and API hosts with token-scoped context instead of internal console headers.WebhooksRegister endpoints, verify signatures, deduplicate events, and handle retries safely.OpenAPI and PostmanImport the public customer collection with id/api hosts, scoped tokens, and environment variables.Status APIRead status summaries, subscribe to updates, and align incident communication with product UX.
Explore by growth workflow
Growth docs stay connected to identity facts: membership, session, project, campaign, loyalty, and lifecycle context.
Segments and audiencesShape audiences from project membership, session, lifecycle, and plan-aware signals.Campaign lifecycleDocument campaign targeting, lifecycle events, delivery boundaries, and campaign plan limits.Loyalty programsConnect loyalty events to Lamba identity context without creating a second customer graph.NotificationsCoordinate lifecycle email, SMS, notification channels, and webhook-backed delivery visibility.
Learn the concepts
Use these pages when you need to explain the model before writing code or designing access rules.
Core conceptsLearn the product language for Workspace, Project, Lamba User, memberships, sessions, and events.Workspaces and ProjectsModel product boundaries, public/private projects, environment separation, and ownership.Roles and permissionsUse Workspace roles, Project console roles, and Project roles on the right surface.Plan enforcementUnderstand MAU, soft limits, hard limits, 402 business-state responses, and upgrade messaging.
Need the full API contract?
Start from the customer API overview, then use OpenAPI and Postman details for request validation.