Update Timecard Entry (Project)
update_timecard_entry_projectUpdate a specific timecard entry in Procore by providing the project ID and entry ID. Modify fields such as hours, cost code, or billable status.
Instructions
Update a specific timecard entry. #### See - Daily Log guide - for additional info on * Attachments. Use this to update an existing Field Productivity records (only the supplied fields are changed). Updates the specified Field Productivity records and returns the modified object on success. Required parameters: project_id, id. Procore API: Project Management > Field Productivity. Endpoint: PATCH /rest/v1.0/projects/{project_id}/timecard_entries/{id}
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| project_id | Yes | URL path parameter — unique identifier for the project. | |
| id | Yes | URL path parameter — iD of the timecard entry | |
| hours | No | JSON request body field — total number of hours worked (excluding breaks) for the timecard entry. This property is not applicable 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 applicable if the tmesheet time entry is configured for start time and stop time. | |
| party_id | No | JSON request body field — the ID of the Party of the Timecard Entry | |
| time_in | No | JSON request body field — the start time of the timecard entry in ISO 8601 format. This property is only applicable 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 applicable 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 dntry in ISO 8601 format. | |
| datetime | No | JSON request body field — the date and time of the record. This property is mutually exclusive with the Date property. | |
| 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. | |
| cost_code_id | No | JSON request body field — the ID of the cost code corresponding to the timecard entry. | |
| login_information_id | No | JSON request body field — the ID of the login information corresponding to the timecard entry. | |
| timesheet_id | No | JSON request body field — the ID of the timesheet corresponding to the timecard entry. | |
| daily_log_segment_id | No | JSON request body field — daily Log Segment ID | |
| clock_in_id | No | JSON request body field — the ID of the clock in GPS position corresponding to the timecard entry. | |
| clock_out_id | No | JSON request body field — the ID of the clock out GPS position corresponding to the timecard entry. | |
| 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 pertaining to the time card entry. |