Projects API

A project groups scoped work for a client into phases and tasks. Use this API to create projects, build out their phase and task structure, manage checklists, and read the tickets attached to a project.

Create a project

Only project_name is required. Attach it to a client with client_id, assign an owner via assigned_to or a team via assigned_team_id, and set start_date and end_date when you have them. The project starts empty; phases and tasks come next.

curl https://algapsa.com/api/v1/projects \
  -H "X-API-Key: $ALGA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "project_name": "Northwind email migration",
    "client_id": "cl_3f9a2c",
    "assigned_to": "usr_5b21",
    "start_date": "2026-07-01"
  }'

Phases and tasks

Work hangs off phases. Add one with POST /projects/{id}/phases, then create tasks inside it via POST /projects/{id}/phases/{phaseId}/tasks. Tasks are addressed directly once they exist — GET /projects/tasks/{taskId} to read one, PUT to update, and POST /projects/tasks/{taskId}/checklist to add checklist items. Status mappings for a project come from GET /projects/{id}/task-status-mappings.

Read across projects

Filter the list with GET /projects, search free-text with GET /projects/search, and pull portfolio totals from GET /projects/stats. To see the service work tied to a project, use GET /projects/{id}/tickets. Bulk routes under /projects/bulk-assign, /projects/bulk-status, and /projects/bulk-update apply changes to many projects at once.

Endpoints

Every endpoint links through to its full parameters, request and response schemas, and code samples.