How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Leadping Events API

Provides a unified record of Leadping activity across communication channels. Use these endpoints to retrieve event timelines, search event history, inspect event details, and record supported application events.

Leadping Events API is one of 29 APIs that Leadping publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Event. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and rate-limit docs.

This API exposes 7 operations across 7 paths, and defines 12 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://api.leadping.ai.

7 operations 7 paths 12 schemas 2 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.leadping.ai
Authentication
HTTP Bearer, HTTP Bearer
License
Terms of Service
Resource Areas
1

Authentication & Security 2

Leadping Events API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT or organization API key) (Bearer). It accepts HTTP bearer tokens (Leadping source key) (SourceKey).

  • Bearer — Authorization header using the Bearer scheme. Accepted values are Leadping user JWT access tokens and WorkOS organization API keys beginning with sk.
  • SourceKey — Leadping source key for lead ingestion endpoints only using the Authorization header. Example: "Authorization: Bearer lpsrc...".

Paths & Operations 7

Across 7 paths, the API surfaces 7 operations — 2 GET, 5 POST. Each is listed below with its method, path, parameters, and response codes.

Events 7

Provides a unified record of Leadping activity across communication channels. Use these endpoints to retrieve event timelines, search event history, inspect event details, and rec…

POST
/events/all/my
List current-user lead events
Events_GetAllForCurrentUser 3 params body → 200400401403429
POST
/events/organizations/{organizationId}
List organization lead event history
Events_GetAllForOrganization 3 params body → 200400401403429
POST
/events/conversations/{conversationId}
List a conversation's event history
Events_GetAllForConversation 1 param body → 200400401403429
POST
/events/leads/{leadId}
List event history for a lead
Events_GetAllForLead 1 param body → 200400401403429
GET
/events/{eventId}
Get lead event details by ID
Events_GetById 1 param → 200404401403429
GET
/events/detail/{eventId}
Get full lead event payload by ID
Events_GetDetailById 1 param → 200404401403429
POST
/events/conversations/{conversationId}/notes
Add a note to a conversation
Events_CreateNote 1 param body → 200400401403429

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are EventTableRow (47 properties), EventDetailResponse (32 properties), RequestDataOptions (8 properties), RangeFilter (5 properties). Each schema is shown below with its type and property counts.

PagedResultOfEventTableRow
object
Returns one page of query results together with page-size, optional total-count, and opaque continuation-cursor metadata.
4 properties
EventDetailResponse
object
Describes event detail data returned by Leadping.
32 properties
RequestDataOptions
object
Defines cursor pagination, sorting, search, exact-match filters, and range filters for a structured API query.
8 properties
EventTableRow
object
Summarizes event timeline data in paginated and searchable results.
47 properties
CreateNoteRequest
object
Defines the input used for create note.
1 property 1 required
MessageMediaAttachment
object
Media attached to an SMS/MMS conversation event.
5 properties
IdNamePair
object
Provides a compact API reference to another resource using its stable identifier and human-readable display name.
2 properties 2 required
OrderByOption
object
Defines one field and direction used to order an API query result set.
2 properties
ExactMatchFilter
object
Selects records whose named field equals a supplied scalar value.
2 properties
RangeFilter
object
Selects records by applying inclusive or exclusive lower and upper bounds to a named comparable field.
5 properties
ProblemDetails
object
Standard problem-details response containing machine-readable and human-readable information about an HTTP API error.
5 properties
EventTimelineType
string
Classifies the kind of activity displayed in a lead or conversation event timeline.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

leadping-events-api-openapi.yml Raw ↑

Other APIs Leadping publishes across the network.

Leadping MCP Servers
Leadping Webhook Events
Leadping Analytics API
Leadping Automations API
Leadping Call Events API
Leadping Calls API
Leadping Contact API
Leadping Conversations API
Leadping Feedback API
Leadping Leads API
Leadping Lead Status Changes API
Leadping Lead Statuses API
Where this information came from

This is an independent, third-party profile of Leadping Events API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.