Cassidy Intake Endpoint
Push action items and takeaways from client calls into the PMT Queue for review.Endpoint
Authentication
Uses the REST API token. Include thel5key header with the client’s API key.
client_id is extracted from the token automatically.
Request
Headers
Body
Send a single JSON object or an array of objects (max 100 per request).Required
Optional — Core Fields
Optional — Categorization
Category / Subcategory Pairings
Sending a subcategory that doesn’t belong to the given category will return a
400 validation error. Subcategory without a category is also rejected.
Optional — Extended Fields
Fields set automatically by the backend
These are not sent by Cassidy:Examples
Single item
Batch (multiple items)
Minimal request (title only)
Responses
201 Created
400 Bad Request (validation errors)
403 Forbidden (invalid or missing API key)
Returned automatically when thel5key header is missing or does not match any active client.
What happens after intake
- Items land in the PMT Queue with
intake_source = "cassidy"andqueue_status = "pending". - A team member views the Cassidy queue tab in the PMT Queue dashboard.
- They click the checkmark to accept (opens a form to fill remaining fields) or the X to reject (soft-deletes with audit trail).
- Accepted items move to the main PMT with
status = "Planned".
.png?fit=max&auto=format&n=Frm2GFbmok4D-yJA&q=85&s=93c3ebd47542af65d1cd06d8563a7f6e)