Getting Started
Enums and Limits
Every fixed value set the API uses, and the size caps to enforce in the client.
Enums
Hard-code these; they are constrained by the database and will not change silently.
| Values | |
|---|---|
| Role | member, super_admin |
| Member status | active, pending, deactivated |
| Reaction | like, dislike, celebrate, support, love, insightful, funny |
| Comment vote | like, dislike |
| Recognition category | teamwork, innovation, above_and_beyond, leadership, customer_focus, learning |
| Notification kind | mention, comment, reply, reaction, recognition, poll_closed |
| Feed scope | all, following, announcements, saved, polls, recognitions |
| Feed sort | latest, top |
| Directory sort | name, recent, posts |
| Team colour | blue, emerald, violet, amber, rose, cyan, orange, slate |
| Work status | in_progress, completed, on_hold |
| Push platform | web, ios, android |
| Department | engineering, product, design, hr, business_development, digital_marketing, finance, operations, support, legal |
department is "" when nobody has set one. Every department keeps a work
timeline of the same shape — only the vocabulary around it changes (the web app
calls it "Projects" in Engineering, "Campaigns" in Marketing), so mirror that
table client-side if you want the same wording.
Limits
Enforce these in the composer so the person is stopped before the request is, and still handle the 400 — the server is the authority.
| Post body | 2000 chars |
| Comment | 1000 chars |
| Images per post | 4 |
| Videos per post | 1 |
| Documents per post | 5 |
| Poll options | 2–6, 80 chars each |
| Poll question / description | 200 / 300 chars |
| Recognition message | 500 chars |
| Bio | 500 chars |
| Current work | 1000 chars |
| Title / location | 120 chars |
| Skills / learning interests | 20 / 10 |
| Timeline entries | 10, with 8 contributions each |
| Page size | 20 default, 50 max |