Public waitlist and usage-count endpoints #74

Closed
opened 2026-10-17 04:07:04 -07:00 by westfarn · 0 comments
Owner

The public site needs two unauthenticated endpoints. Registration is often off, and the landing page must not invent a user count.

Scope

  • POST /api/public/waitlist/ stores an email (idempotent, same response whether the email is new or already stored). Validate the address. No account is created.
  • GET /api/public/usage/ returns active non-deleted account count, document count, and as_of. No emails, names, or avatars.
  • AllowAny with empty authentication classes, same pattern as PublicSettingsView.
  • Tests for validation, idempotency, and counts.

Out of scope

  • Testimonials or avatar storage.
The public site needs two unauthenticated endpoints. Registration is often off, and the landing page must not invent a user count. ## Scope - `POST /api/public/waitlist/` stores an email (idempotent, same response whether the email is new or already stored). Validate the address. No account is created. - `GET /api/public/usage/` returns active non-deleted account count, document count, and `as_of`. No emails, names, or avatars. - `AllowAny` with empty authentication classes, same pattern as `PublicSettingsView`. - Tests for validation, idempotency, and counts. ## Out of scope - Testimonials or avatar storage.
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ai_ml_operations/chat_backend#74