PATCH /rest/v1.0/companies/{company_id}/generic_tools/{generic_tool_id}
Update a Generic Tool's attributes. For more information on Generic Tool and Correspondence Tool endpoints, see Working with the Correspondence Tool.
Servers
- https://api.procore.com
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
company_id |
Integer | Yes |
Unique identifier for the company. |
generic_tool_id |
Integer | Yes |
Unique identifier for the Generic Tool. |
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 |
|---|---|---|---|
generic_tool |
Object | Yes | |
generic_tool.abbreviation |
String | No |
An abbreviation for the generic tool. |
generic_tool.new_project_default |
Boolean | No |
If this property is set to true, the generic tool will be added to new projects by default. |
generic_tool.send_overdue_notifications |
Boolean | No |
If this property is set to true, notifications will be sent to assignees when an item is overdue. |
generic_tool.title |
String | Yes |
The title of the generic tool. |
generic_tool.private_by_default |
Boolean | No |
If this property is set to true, any items that are created for the tool are private by default. |
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.