The resources you'll actually use: /contacts and /accounts (CRUD + search), /sequences (enroll/remove), /signals (fire custom signals), /activities (log and query), /audiences (manage lists), /workflows (trigger runs).
Records
GET/POST/PATCH /contacts and /accounts with rich filter syntax on GET (field operators, tag filters, ICP-score ranges). POST upserts by email/domain match by default — duplicate-safe.
Motion
POST /sequences/{id}/enroll (contact IDs + options), DELETE to remove, GET /sequences/{id}/stats for performance. POST /workflows/{id}/trigger fires a workflow run with a custom payload.
Signals and activities
POST /signals fires a custom signal (your product events become turgo triggers — the highest-leverage endpoint for PLG teams). GET/POST /activities reads and writes timeline entries.
Meta
GET /audiences, /users, /mailboxes/health for operational tooling. The OpenAPI spec is the authoritative parameter reference; this article is the map, not the atlas.
