POST /rest/v1.1/projects/{project_id}/project_timecard_entries/bulk_create
Create timecard entries in a bulk transaction utilizing the Project Timesheet Timecard Entry field set. (Current max is set to 25 timecard entries). NOTE, this endpoint is currently in the experimental stage and is subject to change. Please contact support to be added as a beta participant.
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. |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
timecard_entries[] |
Array | Yes |
Array of timecard entries to be created |
timecard_entries[].line_item_type_id |
Integer | No |
The ID of the Line Item Type of the Timecard Entry. DO NOT provide if providing a wbs_code_id. |
timecard_entries[].project_id |
Integer | No |
The ID of the project to which this Timecard Entry belongs. |
timecard_entries[].timesheet_id |
Integer | No |
The ID of the timesheet to associate this record with. |
timecard_entries[].lunch_clock_in_id |
Integer | No |
If so configured, the ID of the lunch clock in GPS record |
timecard_entries[].description |
String | No |
The Description of the Timecard Entry |
timecard_entries[].set_timecard_time_type_automatically |
Boolean | No |
If so configured and a truthy value supplied, the timecard will have its timecard_time_type_id set automatically and may be split. |
timecard_entries[].clock_in_id |
Integer | No |
If so configured, the ID of the clock in GPS record |
timecard_entries[].clock_in_time |
String | No |
If so configured, the datetime a timecard clock in was punched |
timecard_entries[].hours |
String | No |
If so configured, the hours of the Timecard Entry |
timecard_entries[].clock_out_id |
Integer | No |
If so configured, the ID of the clock out GPS record |
timecard_entries[].party_id |
Integer | No |
The ID of the Party for the Timecard Entry |
timecard_entries[].lunch_stop_time |
String | No |
If so configured, the datetime when lunch stopped |
timecard_entries[].approval_status |
String | No |
The approval status for this Timecard Entry. |
timecard_entries[].date |
String | No |
The Date of the Timecard Entry |
timecard_entries[].origin_data |
String | No |
Value of related external data |
timecard_entries[].lunch_clock_out_id |
Integer | No |
If so configured, the ID of the lunch clock out GPS record |
timecard_entries[].work_classification_id |
Integer | No |
The ID of the work classification for this Timecard Entry. |
timecard_entries[].wbs_code_id |
Integer | No |
The ID of the Task Code for the Timecard Entry. |
timecard_entries[].origin_id |
Integer | No |
ID of related external data |
timecard_entries[].billable |
Boolean | No |
The Billable status of the Timecard Entry Default value: false |
timecard_entries[].timecard_time_type_id |
Integer | No |
The ID of the Timecard Time Type of the Timecard Entry. |
timecard_entries[].lunch_start_time |
String | No |
If so configured, the datetime when lunch started |
timecard_entries[].clock_out_time |
String | No |
If so configured, the datetime a timecard clock out was punched |
timecard_entries[].cost_code_id |
Integer | No |
The ID of the Cost Code of the Timecard Entry. DO NOT provide if providing a wbs_code_id. |
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.