Skip to main content
POST

Overview

A person works a case by sending it an event. Give an action, a note or both: one of the goal’s person_actions, or free text up to 4,000 characters. An action also records the case’s last_event: what, who, when, the inputs and the note. A note alone does not. The event takes the same door as Events with one difference: it wakes an existing case only and never opens one; a key with no case is 404. Each accepted post is written to the organization audit log as org.case_event_posted.

Authentication

A signed-in organization member. A member may post only to the cases they own, where the record’s owner is their email (My cases); an admin may post to any case in the organization.

Path Parameters

string
required
The goal the case belongs to
string
required
The case key

Query Parameters

string
For a key no path segment carries (. and .. fold away in URL parsing): /cases/-/events?key=.., where the segment is a placeholder.

Request Body

string
One of the goal’s person_actions
string
Up to 4,000 characters
object
With action: its inputs from the goal’s case view, by key. A choice read from the case must be one the case offers. Numbers as numbers, times ISO 8601 with a zone. Kept as the case’s recorded

Response

string
already_open when the case was running or waiting, reopened when it had finished and this post reopened it

Errors