POST /rest/v1.0/projects/{project_id}/manpower_logs
Creates single Manpower Log.
See - Daily Log guide - for additional info on
- Attachments
- Locations
Servers
- https://api.procore.com
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
project_id |
Integer | Yes |
Unique identifier for the project. |
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. |
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
run_configurable_validations |
Boolean | No |
If true, validations are run for the corresponding Configurable Field Set. Default value: false |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
manpower_log |
Object | Yes | |
manpower_log.num_workers |
Integer | No |
Number of workers |
manpower_log.location_id |
Integer | No |
The ID of the Location of the Manpower Log. |
manpower_log.notes |
String | No |
Notes |
manpower_log.datetime |
String | No |
Datetime of record. Mutually exclusive with the date property. |
manpower_log.num_hours |
String | No |
Number of hours for each worker |
manpower_log.contact_id |
Integer | No |
ID of the Vendor that is performing work |
manpower_log.date |
String | No |
Date of record. Mutually exclusive with the datetime property. |
manpower_log.user_id |
Integer | No |
ID of the user that is performing work. Use this instead of contact_id when tracking hours for a specific user. |
manpower_log.trade_id |
Integer | No |
ID of the Trade associated to the Manpower Log |
manpower_log.mt_location[] |
Array | No |
Use this for creating a new multi-tier or single-tier Location. This will be ignored if |
manpower_log.cost_code_id |
Integer | No |
Cost Code ID |
manpower_log.custom_field_%{custom_field_definition_id} |
No |
Value of the custom field. The data type of the value passed in corresponds with the data_type of the Custom Field Definition. For a lov_entry data_type the value passed in should be the ID of one of the Custom Field Definition's LOV Entries. For a lov_entries data_type the value passed in should be an array of IDs of the Custom Field Definition's LOV Entries. |
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.