Activates a Contractor Management (CM/CM+) contractor that was previously
deactivated: the employment, the contractor's user account and the latest
contract are reactivated.
Only contractor employments are supported; any other employment type returns
a 422. Contractor of Record (COR) employments cannot be activated through
this endpoint and return a 422.
Requirements:
- The contractor's user account must be inactive.
- The employment status must be
archived. - The requesting user must be allowed to manage this contractor.
When the employment has no product assigned, the standard Contractor
Management product is assigned on activation. Resources deleted by a
previous deactivation (invoices, incentives, automatic payments, time off)
are not restored. A Contractor Plus subscription that was scheduled to end
by the deactivation is not reinstated: the contractor keeps Plus until that
end date and then drops to standard. To keep the contractor on Plus,
upgrade again through the contractor-plus-subscription endpoint after
activation.
On success the employment.user_status.activated webhook is triggered.
Calling this endpoint for an employment that is already active returns a
422 with a descriptive message.
Authentication
This endpoint accepts any one of the following token types:
- Company-scoped access token (
OAuth2AuthorizationCode) — obtained through the Authorization Code flow or the Refresh Token flow. See Authentication for partners. - Customer API token (
CustomerAPIToken) — generated by the customer on their Integration Settings page. See Authorization for customers.
Scopes
| Category | Read only Scope | Write only Scope (read access implicit) |
|---|---|---|
Manage employments (employments) | - | Manage employments (employment:write) |
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||