October 30th, 2025

Breaking changes

Breaking changes are planned for November 8th.

POST: /api/v2/pub/employees

PATCH: /api/v2/pub/employees/{id}

❗️
Removed

field 'account_type' will be removed from the request body

🚧
Changed

field 'account_type_id' will be required

POST: /api/v2/pub/projects

PATCH: /api/v2/pub/projects/{id}

❗️
Removed

fields 'manager_id' and 'executive_id' will be removed from the request body

manager and executive will be replaced by primary contact and secondary contact, but assigning contacts will require a different approach described in Migration notes below

Migration Notes

New API endpoints will be added to support project contact management.

New Endpoints

Assign Primary Contact

PUT: /api/v2/pub/projects/{id}/assign-primary-contact

Assign Secondary Contact

PUT: /api/v2/pub/projects/{id}/assign-secondary-contact

Both endpoints accept the following request body field:

{
  "employee_id": "<string>|<null>"
}

Invite User to a Project

POST: /api/v2/pub/project-directories/{id}/invitations

This endpoint accept the following request body field:

{
  "user_id": "<string>",
}

Assigning a Primary or Secondary Contact

To assign an employee as a primary or secondary contact, follow these steps:

Ensure the employee is already invited to the project.
- This can be done either:
  - Through the UI, or
  - By calling the POST /api/v2/pub/project-directories/{id}/invitations endpoint.
Assign the employee as a contact.
- This can be done either:
  - Through the UI, or
  - By calling one of the following endpoints:
    - PUT /api/v2/pub/projects/{id}/assign-primary-contact
    - PUT /api/v2/pub/projects/{id}/assign-secondary-contact