Meetyy API Documentation

Auth, 2FA, OAuth, profiles, onboarding, admin approval, verification documents.

Rules, off-days, precomputed slots, nightly generation, 10-min holds.

Free + paid (fake checkout) lifecycle, package follow-ups, auto-complete & auto-expire.

1:1 chat threads, file attachments, in-chat calendar sharing & appointment booking.

Memberships, subscriptions (fake checkout), XP & levelling, feeds, gated courses.

Modules, lessons, multi-audience pricing, progress tracking, reviews, storefront, and the management rail (students, coursework, notices, materials, notes, discussion).

Unified feed, mutual connections, suggested profiles, posts/reactions/comments/shares, polls, engagement ranking.

Tiered benefits (JSONB), free-session credits, billing.

Personal AI agents with context injection and todos.

Mentor-side data-driven suggestions.

Email + in-app + push, reviews, admin dashboard.

Performance, webhooks, rate limiting, audit logs, GDPR.

Approve / reject / suspend / reinstate, with approval and rejection notifications now dispatching — the three §4.4 data-loss defects and the suspension audit entry are still outstanding.

Admin review queue, authenticated download, and approve/reject with notes, all notifying the mentor; the §5.3 audit entry for each download is not yet written.

Mentee browsing plus role-agnostic suspend (is_active), ban (is_banned), and reinstate with token revocation, transactional audit entries, and email. Status is derived via UserAccountStatus rather than the account_status column §6.2 specifies, so suspensions cannot be time-boxed.

Profile reports are live at /admin/user-reports — grouped by reported member, with dismiss / warn / uphold / escalate closing every pending report in one audited decision. Post and comment triage plus moderation_status takedown are still pending.

Append-only admin_audit_logs table, model, all 15 action cases, and AuditLogService are live, but only account moderation writes to it; mentor/document/content wiring and the §8.3 read endpoint are pending.

Mentor registered/approved/rejected, document reviewed, and account suspend/ban/reinstate all dispatch. Mentor suspension/reinstatement and content moderation notifications exist as classes but are wired to nothing.

app/Policies/Admin with explicit registration — AccountModerationPolicy and CommunityTagPolicy live; the moderator role is not seeded, so the admin/moderator split is unenforced.

permission:{name} middleware per route once the platform-wide permission design is settled. The gate is still role:admin and the seven seeded permissions are enforced nowhere.

Vue 3 SPA at /admin consuming the admin API and nothing else — sign-in with 2FA, mentor review, mentee browsing, account moderation, document review, and community tags. Adds no backend surface.

CRUD over the discovery tag set community owners pick from, with an explicitly registered policy. Shipped outside the BRD and writes no audit entry.