Skip to main content

Imported from STAKEHOLDER_API_STATUS_2026-02-24.md. Edit source file, then re-run sync.

Nova API Status Update

Date: February 24, 2026
Audience: Product, Engineering Leadership, Operations, GTM

Executive Summary​

The API is near complete for core MVP workflows.

  • Core platform capabilities (auth, workspaces, assistants, connections, senders, conversations/messages, webhooks, queueing, workers, admin ops) are implemented and operational.
  • Critical reliability infrastructure is in place (BullMQ workers, queue operations, reprocessing controls, infra-backed E2E coverage, CI workflow).
  • Managed mailbox lifecycle and IMAP/Gmail history ingestion foundations are implemented, with deterministic sync cursor handling.

Current assessment: API is approximately 85-90% complete for MVP production readiness, with remaining work concentrated in operational hardening and UX parity (mostly dashboard-facing surfaces).

What Is Done​

1) Core API Platform​

  • NestJS monolith architecture established and stable.
  • JWT auth + role guards active across protected surfaces.
  • Core domain modules implemented: assistants/agents, users, workspaces, contacts, conversations, messages, connections, senders.
  • Swagger/OpenAPI documentation endpoint available.

2) Messaging and Email Flows​

  • Outbound send pipeline implemented end-to-end via action queue -> delivery queue.
  • Conversation send endpoint implemented and validated.
  • Generic SMTP provider path supported in delivery worker.
  • Webhook ingress and signature verification implemented for key channels/providers.
  • Attachment upload URL endpoint implemented (S3-compatible presign).

3) Mailbox Provisioning and Sync​

  • Mailcow adapter + mailbox provisioning orchestrator implemented.
  • Assistant lifecycle integrated with managed mailbox operations (provision/deprovision/suspend/reactivate/reset-password).
  • Lifecycle operations now queue-backed with persisted lifecycle run tracking and retry support.
  • Gmail and generic IMAP sync jobs implemented (full + incremental) with deterministic cursor semantics and rollover fallback.

4) Reliability and Operations​

  • Queue control APIs live (stats, pause, resume, drain).
  • Failed-job listing and retry APIs live (bulk + per-job).
  • Reprocessing APIs live with run persistence and safety controls.
  • Admin metrics endpoint implemented (queue depth + worker aggregates).
  • Workspace scoping and super-admin override behavior hardened for admin operations.

5) Test and CI Coverage​

  • Infra-backed API E2E runner implemented (Mongo + Redis health-gated startup).
  • Critical E2E suite includes send lifecycle, queue ops/reprocessing, connections lifecycle, IMAP sync, managed mailbox lifecycle.
  • CI workflow runs build/unit + infra E2E subset + dependency audit hooks.

Remaining Work (API-side)​

High Priority​

  1. Expand E2E to remaining critical paths (notably auth exchange edge cases and ingress signature/error-path coverage).
  2. Add deeper retry/DLQ policy assertions for provisioning/history jobs.
  3. Promote observability from in-memory endpoint metrics to persistent telemetry (Prometheus/OpenTelemetry path).

Medium Priority​

  1. Finalize production mail topology and operational runbooks (Mailcow/deployment/deliverability decisions).
  2. Complete online dependency audit and controlled upgrades in network-enabled CI.

Out of Scope for “API completeness” but still pending​

  • Dashboard parity work (rules editor/events viewers/connection diagnostics) is still incomplete; this is primarily UI/API-client integration work, not core backend capability.

Risk Summary​

  • Primary delivery risk: production operations hardening (telemetry, alerting, deliverability runbooks), not core feature implementation.
  • Secondary risk: documentation drift between historical tracker sections and current monolith endpoints can create planning confusion.

Milestone A (1 sprint): API hardening closeout​

  • Add missing auth + ingress E2E cases.
  • Implement retry/DLQ policy validation tests.
  • Finalize dependency audit run in CI.

Milestone B (1 sprint): Ops readiness​

  • Add persistent metrics export and baseline alert rules.
  • Publish incident runbooks for queue saturation, worker failures, delivery failures.

Milestone C (parallel): Dashboard parity​

  • Wire dashboard events/monitoring/connection diagnostics to existing API endpoints.

Bottom Line​

Yes, the API is near complete for core product operation. The remaining work is mostly production hardening and observability maturity, plus dashboard parity to expose existing backend capabilities cleanly to operators.