PATCH /rest/v1.0/projects/{project_id}/drawing_revisions/{id}
Update specified Drawing Revision
Servers
- https://api.procore.com
Path parameters
Name | Type | Required | Description |
---|---|---|---|
id |
Integer | Yes |
ID of the Drawing Revision |
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 |
---|---|---|---|
drawing_revision |
Object | Yes |
Drawing Revision |
drawing_revision.drawing_date |
String | No |
Drawing date |
drawing_revision.floorplan |
Boolean | No |
Revision floorplan status |
drawing_revision.drawing_set_id |
Integer | No |
Drawing Set ID |
drawing_revision.received_date |
String | No |
Received date |
drawing_revision.revision_number |
String | No |
Revision number |
drawing_revision.drawing_id |
Integer | No |
Drawing ID |
drawing_revision.custom_field_%{custom_field_definition_id} |
No |
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 of the Custom Field Definition's LOV Entries. For a lov_entries data_type the value passed in should be an array of IDs of the Custom Field Definition's LOV Entries. |
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.