Super People
Documentation for the Super People API, its web and mobile clients, and running it in production.
The mobile app and the web app talk to the same API — there is no separate mobile backend. Only the session differs: the web app sends a cookie, the mobile app sends a bearer token.
- Interactive API reference (always current):
GET /api/v1/docs - Machine-readable spec:
GET /api/v1/openapi.json - Base URLs:
http://localhost:3101local,https://api-peoples.superlabs.coproduction
Getting Started
How the API works across every module. Read Authentication and Conventions first.
| Page | Covers |
|---|---|
| Getting Started | Environments, the spec, generating a typed client |
| Authentication | Sign in, the bearer token, session lifetime, 401, sign out |
| Conventions | Paging, errors, dates and ids, request bodies |
| Roles and Visibility | Member vs super admin |
| Media | Uploading and resolving images, videos, documents |
| The Content Model | Mentions, hashtags, posts, reactions, polls, recognitions, comments |
| Notifications and Live Updates | Push, the unread badge, the SSE stream |
| Enums and Limits | Fixed value sets and size caps |
| Client Structure and Checklist | Suggested layout and pre-ship checks |
| Grievance Channel walkthrough | The grievance flow end to end |
API Reference
One page per module — endpoints plus the models they use. See the full module list.
Operations
| Page | For |
|---|---|
| Backend Configuration | Environment variables clients depend on |
| Browser push smoke test | The real-browser check after a push-related release |