Create Action Plan Item Assignee Signature
create_action_plan_item_assignee_signatureCreate a signature for an action plan item assignee. Provide project and assignee IDs, along with an attachment or base64 PNG string, to generate and return the new signature record.
Instructions
Create a single Action Plan Item Assignee Signature. Note that only one of attachment or attachment_string may be passed when creating a signature, not both. Pass the record's fields as top-level arguments — they are nested under "signature" in the request payload for you. project_id defaults to the value set by procore_set_config when omitted, and plan_item_assignee_id must identify an existing parent record — resolve it with the matching list tool first. Creates the action plan item assignee signature and returns it with its new id (HTTP 201); calling it again creates another record. 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: project_id, plan_item_assignee_id, attachment, attachment_string. Procore API: Project Management > Action Plans. Endpoint: POST /rest/v1.0/projects/{project_id}/action_plans/plan_item_assignees/{plan_item_assignee_id}/signature
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| attachment | Yes | JSON request body field — attachment representing the Signature. To upload an attachment you must upload the entire payload as `multipart/form-data` content-type with the `attachment` file. | |
| project_id | Yes | URL path parameter — unique identifier for the project. | |
| attachment_string | Yes | JSON request body field — base64 encoded string representing PNG image of signature | |
| plan_item_assignee_id | Yes | URL path parameter — action Plan Item Assignee ID |