POST /rest/v1.0/projects/{project_id}/action_plans/plan_test_records
Create an Action Plan Test Record
Action Plan Test Records can have one of the following payload formats (checklist_id, form_id, generic_tool_id, meeting_id, submittal_log_id, observation_item_id, attachment) Attachment payloads must be a binary file or contain an attachment_id, upload_id, drawing_revision_id, file_version_id, form_id, or image_id.
A specific Action Plan Test Record Type can only leverage its corresponding format.
*For instance, Checklist Test Records can only leverage checklist_id while Attachment/Photo Test Records can only leverage attachment.
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_test_record |
Object | Yes | |
plan_test_record.plan_item_id |
Integer | Yes |
ID of the associated Action Plan Control Activity |
plan_test_record.payload |
Object | Yes | |
plan_test_record.type |
String | Yes |
Action Plan Test Record Type Possible values:
|
plan_test_record.plan_test_record_request_id |
Integer | Yes |
ID of the associated Action Plan Test Record Request |
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.