Get History Item

GET 
/v1/open-api/lead-event/:eventId

Re-read a single history record, scoped to the token's company (not to a single lead — eventId + dataType already uniquely identify a record within a company). The response is one LeadEventJournalDTO, in the exact shape it has inside the filter endpoint's page.

dataType is required: eventId is not unique across data types (a note and a task can share the same underlying ID), so a record is identified by the (dataType, eventId) pair — both values come from a prior filter response.

⚠️ When dataType = LEAD_TASK, an open task whose deadline hasn't arrived yet is still returned here even though it never appears in the filter endpoint's page (§ filter description) — this endpoint reads directly by ID.

Requires grant PERMISSION_OPEN_API_LEAD:READ.

Request

Responses

200

The history record.

400

Validation error (400). Field-level failures are listed in errors[] and error is null; a malformed / unparsable JSON body is the inverse — error.messageCode is 3705 and errors[] is empty.

401

Invalid, revoked or expired token (401) — also returned when the connection was revoked or the company is blocked.

Produced by the authentication filter, so the body is a reduced envelope: no error, no requestId, and errors is null rather than []. Every cause yields the same fixed English message.

403

The token lacks the required permission:scope grant (403).

404

Resource not found (404).

409

Referenced resource not found (409). Used by the lead history endpoints instead of 404 for a missing lead, record, note or task — this is the repository's existing convention (LeadNotFoundException is also 409), not a considered design choice.

429

Rate limit of 60 requests/minute exceeded (429). Like 401, this comes from the authentication filter: reduced envelope, fixed English message, no error object and no Retry-After header.