Create Timecard Entry
create_timecard_entry_projectCreate a timecard entry for a specific project in Procore. Log hours, dates, cost codes, and custom fields to record field productivity.
Instructions
Create Timecard Entry associated with the specific Project. Use this to create a new Field Productivity records in Procore. Creates a new Field Productivity records and returns the created object on success (HTTP 201). Required parameters: project_id. Procore API (v1.1): Project Management > Field Productivity. Endpoint: POST /rest/v1.1/projects/{project_id}/project_timecard_entries
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| project_id | Yes | URL path parameter — unique identifier for the project. | |
| hours | No | JSON request body field — total number of hours worked (excluding breaks) for the timecard entry. This property is not required if the timesheet time entry is configured for start time and stop time. | |
| lunch_time | No | JSON request body field — the duration of the lunch break, in minutes, for the Timecard Entry. This property is only required if the timesheet time entry is configured for start time and stop time. | |
| time_in | No | JSON request body field — the start time of the Timecard Entry in ISO 8601 format. This property is only required if the timesheet time entry is configured for start time and stop time. | |
| time_out | No | JSON request body field — the stop time of the Timecard Entry in ISO 8601 format. This property is only required if the timesheet time entry is configured for start time and stop time. | |
| billable | No | JSON request body field — the billable status of the Timecard Entry. Must be either true or false. | |
| date | No | JSON request body field — the date of the Timecard Entry in ISO 8601 format. | |
| description | No | JSON request body field — the description of the Timecard Entry. | |
| timecard_time_type_id | No | JSON request body field — the ID of the Timecard Time Type corresponding to the Timecard Entry property. | |
| timesheet_id | No | JSON request body field — the ID of the Timesheet corresponding to the Timecard Entry property. | |
| cost_code_id | No | JSON request body field — the ID of the Cost Code corresponding to the Timecard Entry property. | |
| sub_job_id | No | JSON request body field — the ID of the Subjob corresponding to the Timecard Entry property. | |
| location_id | No | JSON request body field — the ID of the Location corresponding to the Timecard Entry property. | |
| login_information_id | No | JSON request body field — the ID of the Login Information corresponding to the Timecard Entry property. | |
| party_id | No | JSON request body field — the ID of the Party corresponding to the Timecard Entry property. | |
| origin_id | No | JSON request body field — the ID of the related external data. | |
| origin_data | No | JSON request body field — the value of the related external data. | |
| line_item_type_id | No | JSON request body field — the ID of the line item type corresponding to the time card entry. | |
| custom_field_%{custom_field_definition_id} | No | JSON request body field — 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 ... |