Update Case Task
Close, reopen, or reassign a follow-up task
status to close or reopen it, due_at to move its
deadline, assignee to hand it to someone else. At least one field is required.
Statuses
done and dismissed both close the task and stamp completed_at. Setting open
or in_progress on a closed task reopens it and clears completed_at.
This works on any team-side task of the case, including the ones Penbox created
itself — so your integration can close a Penbox follow-up once your side has done
the work.
Tasks assigned to a contact are read-only through the API: they close when the
contact submits the form Penbox sent them. Updating one returns 403, and so does
moving a team-side task onto a contact.
dismissed for “this no longer needs doing”.Authorizations
API token (starts with pnbx_). Create at https://app.penbox.io/workspace/settings/api. Include as: Authorization: Bearer {token}
Body
The task status. done and dismissed both close it.
open, in_progress, done, dismissed "done"
New due date, or null to clear it.
The workspace member the task is assigned to, resolved by email. Silent members resolve too. Pass null to leave the task unassigned.
Response
Task updated
Task UUID
When the task was created
The case this task belongs to
The kind of task. manual for every task created through the API. Tasks Penbox creates by itself carry their own key, such as fill_form, review or follow_up.
"manual"
What has to be done. Empty on some Penbox-created tasks, which Penbox labels from their type in the reader language.
Optional detail
Current task status
open, in_progress, done, dismissed Due date
When the task was closed
The case step that spawned the task, when Penbox created it
Who has to close the task. null when unassigned.