Contents
Changelog
May 21st, 2026
Announced: May 21, 2026
May 21st, 2026
What is changing?
Projects, project boards, phases, tasks, and project fields are now available in API v2. This update brings the projects domain in line with the rest of v2 — ISO timestamps, predictable response shapes, and the same conventions you already use for deals, persons, and organizations.
Pairs with the project webhooks we shipped earlier — projects now have full v2 + webhooks coverage.
Summary of the new endpoints
The Projects API v2 includes the following endpoints:
Projects:
GET /api/v2/projectsGET /api/v2/projects/{id}GET /api/v2/projects/archivedPOST /api/v2/projectsPOST /api/v2/projects/{id}/archivePATCH /api/v2/projects/{id}DELETE /api/v2/projects/{id}
GET /api/v2/projects also supports new quick filters: deal_id, person_id, and organization_id for fetching projects linked to a specific record.
Project Boards:
GET /api/v2/boardsGET /api/v2/boards/{id}POST /api/v2/boardsPATCH /api/v2/boards/{id}DELETE /api/v2/boards/{id}
Project Phases:
GET /api/v2/phasesGET /api/v2/phases/{id}POST /api/v2/phasesPATCH /api/v2/phases/{id}DELETE /api/v2/phases/{id}
Project Tasks:
GET /api/v2/tasksGET /api/v2/tasks/{id}POST /api/v2/tasksPATCH /api/v2/tasks/{id}DELETE /api/v2/tasks/{id}
Tasks in v2 use assignee_ids (array) instead of the legacy assignee_id field, and timestamps are returned in ISO 8601 format.
Project Templates (read-only):
Project Fields:
GET /api/v2/projectFieldsGET /api/v2/projectFields/{field_code}POST /api/v2/projectFieldsPATCH /api/v2/projectFields/{field_code}DELETE /api/v2/projectFields/{field_code}POST /api/v2/projectFields/{field_code}/optionsPATCH /api/v2/projectFields/{field_code}/optionsDELETE /api/v2/projectFields/{field_code}/options
Additional new endpoints:
GET /api/v2/projects/{id}/changelogGET /api/v2/projects/searchGET /api/v2/projects/{id}/permittedUsers
If you have any questions or comments, feel free to let us know in the Developer's Community.