Update Company File
update_company_fileUpdate a company file in Procore by modifying its fields, creating a new version. Specify only the fields to change, with company_id and id required.
Instructions
Update a specific File (creates a new file version). Send only the fields you intend to change; omitted fields keep their current values. Pass the record's fields as top-level arguments — they are nested under "file" in the request payload for you. company_id defaults to the value set by procore_set_config when omitted, and id must identify an existing parent record — resolve it with the matching list tool first. Returns the modified company file on success. Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve. Required parameters: company_id, id. Procore API: Core > Documents. Endpoint: PATCH /rest/v1.0/companies/{company_id}/files/{id}
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | URL path parameter — unique identifier of the Documents resource | |
| data | No | JSON request body field — [DEPRECATED] File to use as file data. Please use upload_uuid instead. Note that it's only possible to post a file using a multipart/form-data body (see RFC 2388). Most HTTP libraries will do the r... | |
| name | No | JSON request body field — the Name of the file | |
| parent_id | No | JSON request body field — the ID of the parent folder to move the file to | |
| company_id | Yes | URL path parameter — unique identifier for the company. | |
| is_tracked | No | JSON request body field — status if a file should be tracked (true/false) | |
| description | No | JSON request body field — a description of the file | |
| upload_uuid | No | JSON request body field — uUID referencing a previously completed Upload. This is the recommended approach for file uploads. See Company Uploads or Project Uploads endpoints for instructions on how to use uploads. You sho... | |
| checked_out_until | No | JSON request body field — check out a file until the specified time. Admins may reset checkout by sending "null" | |
| explicit_permissions | No | JSON request body field — set file to private (true/false) | |
| 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 ... |