Ingest Event
Ingest a first-party event.
Every well-formed event is accepted and stored, whether or not its subject
can be correlated to a known contact or company: correlation is best-effort
and runs asynchronously. Replaying the same external_event_id (or the
exact same event content) is idempotent: the event is accepted but never
stored or processed twice.
Requires the events:write scope on the API key.
Authorizations
Bearer API key issued from Settings → Developers.
Body
Ingest Event payload
Custom event name (1–255 characters).
1 - 255RFC 3339 timestamp when the event occurred.
Event subject identifiers; at least one field is required.
Optional stable identifier from the caller's system, used for idempotent replays.
255Free-form JSON attributes for the event.