Log external activities and events to a target’s activity history. This enables you to track actions from other platforms (RSVPs, event attendance, petition signatures) and in-person activities (doorknocking, meetings).
Activities can be simple standalone events or linked to Activity Entities (representations of external concepts like events or petitions) for more structured, queryable data.
You’ll need to provide the external ID of the target. Activities can be marked as upsertable to update existing records.
For detailed documentation including Activity Entities and advanced examples, see the support guide: “Storing activity history”
{
"external_id": "M123",
"activities": [
{
"external_id": "Event123",
"upsert": true,
"topic": "doorknocking",
"title": "Attended a doorknocking event",
"source": "doorknocking_app",
"body": "Attended the event ...",
"happened_at": "2023-02-01T09:33:00Z"
}
]
}
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
200A successful response
400One or more of the activities is incorrect, or missing required fields
404The target identified in the payload could not be found
