POST /rest/v1.0/projects/{project_id}/delay_logs
Creates single Delay Log.
See - Daily Log guide - for additional info on
- Attachments
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 |
---|---|---|---|
delay_log |
Object | Yes | |
delay_log.end_time_hour |
Number | No |
Number between 0 and 23 representing hour of day |
delay_log.start_time_minute |
Number | No |
Number between 0 and 59 representing minute |
delay_log.start_time |
String | No |
Time when the delay started, Format: HH:MM Example: 21:39 |
delay_log.daily_log_header_id |
Integer | No |
Daily Log Header ID |
delay_log.end_time_minute |
Number | No |
Number between 0 and 59 representing minute |
delay_log.date |
String | No |
Format: YYYY-MM-DD Example: 2016-04-19 |
delay_log.location_id |
Integer | No |
The ID of the Location of the Log. |
delay_log.start_time_hour |
Number | No |
Number between 0 and 23 representing hour of day |
delay_log.datetime |
String | No |
Datetime of record. Mutually exclusive with the date property. |
delay_log.delay_type |
String | No |
Type of delay |
delay_log.comments |
String | No |
Additional comments |
delay_log.mt_location[] |
Array | No |
Use this for creating a new multi-tier or single-tier Location. This will be ignored if |
delay_log.end_time |
String | No |
Time when the delay started, Format: HH:MM Example: 21:39 |
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.