SB Relaxing Club API
Integration guides and a complete endpoint reference for the Go service behind the Relaxing Club mobile and admin applications.
How a request moves through the system
The API is a modular monolith: one Go process routes a request to a feature module, which authorizes the action, applies its domain rules, and uses PostgreSQL for durable state. External services handle email, object storage, push delivery, and meeting media where configured.
What the API currently does
The service supports member registration and email-code login; provider and listing discovery; provider onboarding and menu management; member and guest orders; payment attempts and manual payment review; chat; media upload authorization; community moments and moderation; lifestyle profiles and LiveKit meetings; notifications; provider dashboards and sales; accountant reports; and administrative operations.
The route index is generated from API/openapi/openapi.yaml and synchronization compares every OpenAPI method/path with the Go router. The OpenAPI schemas are still incomplete for some implemented request bodies. Where that happens, use the handler behavior and module guide as the detailed source until the schema is filled in.
A practical reading order
| If you need to… | Read… |
|---|---|
| Make your first API call | Getting started |
| Implement sign-in or token refresh | Authentication and access |
| Understand record ownership and state changes | API workflows |
| Find a route, request field, or response status | Endpoint reference |
| Understand transactions and module boundaries | API architecture |
| Configure staging or production | Production operations |
See the domain glossary for the exact meanings of provider, listing, order, payment, sale, and other domain terms.