Authentication
Most API routes require an authenticated session cookie. Mutation routes validate method, session role, and same-origin request context.
Reference for platform API concepts, authentication expectations, request formats, and example endpoints used by the portal.
Most API routes require an authenticated session cookie. Mutation routes validate method, session role, and same-origin request context.
GET /api/platform-data returns scoped project, client, and invoice data. PATCH /api/projects/[id] updates project status or assignment for allowed roles.
PATCH /api/tasks/[id] updates a single task by unique task ID and recalculates only its parent project progress.
POST /api/invoices creates invoices for existing clients. GET /api/invoices/[id] returns a scoped invoice. GET /api/invoices/[id]/download returns a CSV invoice file.
GET /api/tickets returns scoped support tickets. POST /api/tickets creates client requests. POST /api/tickets/[id]/messages appends replies.
{ "client": "Client Partner", "amount": 25000, "status": "Pending", "dueDate": "2026-06-01" }{ "completed": true }{ "body": "We are reviewing this request now." }