Migrating to v2

What changed in the v2 operations, and what stays on v1.

v2 is additive. It re-issues only the operations whose contract changed; every other operation stays on /construction/admin/v1 and is unaffected. You can call both base paths from the same integration.

Operations that moved to v2

Operation	v1	v2
`POST projects/:projectId/users:import`	Deprecated	Accepts a plain 2-legged token
`POST projects/:projectId/roles:sync`	Available	Re-issued in v2

Import project users

The v1 import operation required a user context: a 3-legged token, or a 2-legged token with the User-Id header. The v2 operation adds plain 2-legged (account:write) as an accepted flow, so back-end integrations no longer need an admin to impersonate.

Switching the import call to v2

- POST /construction/admin/v1/projects/:projectId/users:import
- Authorization: Bearer <2-legged token>
- User-Id: <admin user id>
+ POST /construction/admin/v2/projects/:projectId/users:import
+ Authorization: Bearer <2-legged token>

The v1 operation is marked deprecated and still works; new integrations should target v2.

Sync project roles

POST projects/:projectId/roles:sync is re-issued unchanged in shape and still requires an impersonated or 3-legged token with account:read. Point new code at the v2 path so role syncing and user importing sit on the same version.

Everything else — projects, companies, hub users, project users, the lifecycle operations and the sync-status pollers — remains v1 only. Switch the version selector to v1 to browse them.