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.
Request body
Response
Successful Response
Changes
Changed in 1 of the 12 revisions of this API.376
- ▲
added the new required request property
event_namenew-required-request-property
- ▲
added the new required request property
occurred_atnew-required-request-property
- ▲
removed the required property
idempotencyKeyfrom the response with the202statusresponse-required-property-removed
- ●
removed the request property
eventNamerequest-property-removed
- ●
removed the request property
externalEventIdrequest-property-removed
- ●
removed the request property
occurredAtrequest-property-removed
- ●
removed the request property
subject/companyDomainrequest-property-removed
- ●
removed the request property
subject/externalCompanyIdrequest-property-removed
- ●
removed the request property
subject/externalContactIdrequest-property-removed
- ●
removed the request property
subject/linkedinUrlrequest-property-removed
- ○
added the new optional request property
external_event_idnew-optional-request-property
- ○
added the new optional request property
subject/company_domainnew-optional-request-property
- ○
added the new optional request property
subject/external_company_idnew-optional-request-property
- ○
added the new optional request property
subject/external_contact_idnew-optional-request-property
- ○
added the new optional request property
subject/linkedin_urlnew-optional-request-property
- ○
added the required property
idempotency_keyto the response with the202statusresponse-required-property-added
- ▲