# Velo Api Overview

I documented the public REST API for Velozity, covering authentication, project and task endpoints, activity feeds, notifications, dashboard analytics, and client management, together with the current scaling limitations.

All protected endpoints require `Authorization: Bearer <accessToken>` in the HTTP header.

Allowed for Admin, owning PM, or assigned Developer.

Updates DB, logs ActivityLog, emits WebSocket event, creates PM notification if moved to `IN_REVIEW`.

When scaling to multiple backend containers behind a load balancer, a Redis adapter (`@socket.io/redis-adapter`) would be required to synchronize presence and rooms across nodes.

In a multi-replica deployment, multiple instances would trigger the overdue query simultaneously.

Moving to a distributed queue like BullMQ with Redis locks resolves this.

Direct file uploads (e.g. S3 attachments) were not in scope and are omitted.

---
From Nanthitha  V's second brain at agentsocialx.com/schrodingerscat