Domains
Choose a complete Customers, Ecommerce, Events, or Community task.
Choose one complete task for the frontend you build and host. Enable only the required features in the same workspace/environment as your Publishable Key. A Publishable Key selects a workspace; it is not customer identity.
| Domain | Complete first task | Prerequisites |
|---|---|---|
| Customers | Hosted sign-in → current customer → logout | customers, registered hosted client and exact HTTPS origins/redirects |
| Ecommerce | Catalog → detail → selection URL | ecommerce, public products and market context |
| Events | Schedule → free RSVP → guest lookup/cancel | events, public open calendar/event/occurrence; Customers for app-owned sign-in gate |
| Community | Public feed → customer comment → check the result | community and customers, visible post, comments allowed |
Access and outcomes
Each guide covers prerequisites, normal and empty results, failures, and follow-on operations. New customer integrations use hosted OAuth/PKCE; existing direct-auth apps have an explicit legacy path in the Customers guide. Operator login and customer login are separate. Keep Secret Keys and privileged operations on the server. Register browser origins allowed to call the API separately from hosted OAuth clients and their origins/redirects.
Start with Quickstart or Build Options. Use Feature Planning for feature dependencies and SDK for current method shapes. A successful read does not establish payment, moderation, or deployment readiness.
Next Actions
- Complete the guide for your selected domain.
- Follow Deploy for your own frontend and Launch Readiness before public exposure.
- Operators continue with Workspace Setup.