Update Image
update_imageUpdate an existing image in a Procore project by sending only the fields to change. Provide image ID and project ID to apply changes and retrieve the updated image.
Instructions
Update an existing Image in a Project. 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 "image" in the request payload for you. id must identify an existing parent record — resolve it with the matching list tool first. Returns the modified image 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: id, project_id. Procore API: Project Management > Photos. Endpoint: PATCH /rest/v1.0/images/{id}
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | URL path parameter — unique identifier of the Photos resource | |
| private | No | JSON request body field — the Private status of the Image. Defaults to a project configuration. | |
| log_date | No | JSON request body field — the log date in YYYY-MM-DD format | |
| trade_ids | No | JSON request body field — an array of IDs of the Trades of the Image | |
| project_id | Yes | Query string parameter — unique identifier for the project. | |
| description | No | JSON request body field — image description | |
| location_id | No | JSON request body field — if you want to use an existing location and you have the ID of that existing location use this. `location_id` takes precedence over `mt_location` | |
| mt_location | No | JSON request body field — use this for creating a new multi-tier or single-tier Location. This will be ignored if `location_id` is provided. | |
| image_category_id | No | JSON request body field — image Category ID to move the Image to | |
| daily_log_segment_id | No | JSON request body field — daily Log Segment ID |