POST /rest/v1.0/projects/{project_id}/action_plans/plan_references
Create an Action Plan Reference
Servers
- https://api.procore.com
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
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 |
|---|---|---|---|
plan_reference |
Object | Yes | |
plan_reference.plan_item_id |
Integer | Yes |
Action Plan Item ID |
plan_reference.payload |
Object | Yes |
One of attachment, drawing_revision_id, file_version_id, specification_section_id, submittal_log_id, generic_tool_item_id, form_id, meeting_id, or observation_item_id is accepted depending on the type provided |
plan_reference.payload.specification_section_id |
Integer | No |
Specification Section ID |
plan_reference.payload.observation_item_id |
Integer | No |
Observation Item ID |
plan_reference.payload.file_version_id |
Integer | No |
File Version ID |
plan_reference.payload.drawing_revision_id |
Integer | No |
Drawing Revision ID |
plan_reference.payload.form_id |
Integer | No |
Form ID |
plan_reference.payload.submittal_log_id |
Integer | No |
Submittal Log ID |
plan_reference.payload.meeting_id |
Integer | No |
Meeting ID |
plan_reference.payload.generic_tool_item_id |
Integer | No |
Generic Tool Item (Correspondence) ID |
plan_reference.type |
String | Yes |
Action Plan Reference Type Possible values:
|
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.