POST /rest/v1.0/workforce-planning/v2/companies/{company_id}/people/{person_id}/user
Enable a Person to log in after they have already been created
Servers
- https://api.procore.com
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
person_id |
Integer | Yes |
Unique identifier for the person |
company_id |
Yes |
Unique identifier for the company. This parameter accepts both formats:
A proxy layer automatically handles both formats, but using the Procore company ID is preferred for consistency with other Procore APIs. |
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Procore-Company-Id |
Integer | Yes |
Unique company identifier associated with the Procore User Account. |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
no_invite |
Boolean | No |
If |
email |
String | No |
The email the Person will use to log in. If the Person already has an email in LaborChart, this can be omitted. If no email is on record, this becomes required. |
password |
String | No |
The password the Person will use to log in. If omitted, the Person will receive an email from LaborChart instructing them to set up a password. If provided, no email will be sent. Passwords must meet complexity requirements: - At least 1 uppercase letter - At least 1 lowercase letter - At least 1 number - Minimum length of 8 characters |
permission_level_id |
String | Yes |
UUID of the Permission Level that defines the user's access. |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.