Manages automated lead follow-up workflows and their execution history. Use these endpoints to configure SMS automation steps, preview eligible leads, run workflows, and inspect individual automation executions.
Leadping Automations API is one of 29 APIs that Leadping publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Automations. 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
9 operations
across 7 paths,
and defines 27 schemas.
It is described by OpenAPI 3.2.0, at version v1.
Requests are made against a single base URL, https://api.leadping.ai.
9 operations7 paths27 schemas1 DELETE3 GET4 POST1 PUT
Metadata
The identity and technical contract details declared by the specification.
Leadping Automations 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 9
Across 7 paths, the API surfaces 9 operations — 1 DELETE, 3 GET, 4 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
Automations 9
Manages automated lead follow-up workflows and their execution history. Use these endpoints to configure SMS automation steps, preview eligible leads, run workflows, and inspect i…
POST
/automations
Create an organization lead follow-up automation
Automations_Createbody→ 201400401403429
PUT
/automations/{id}
Update an organization lead follow-up automation
Automations_Update1 parambody→ 200400404401403429
GET
/automations/{id}
Get an organization lead follow-up automation
Automations_Get1 param→ 200404401403429
DELETE
/automations/{id}
Delete an organization lead follow-up automation
Automations_Delete1 param→ 200404401403429
GET
/automations/{id}/runs
Gets recent persisted execution runs for an automation console.
Automations_GetRuns1 param→ 200401403429
GET
/automations/{id}/runs/{runId}
Gets one persisted automation execution run for its console.
The contract defines 27 schemas that model the data the API accepts and returns. The most detailed are AutomationWorkflowRunResponse (27 properties), AutomationResponse (22 properties), AutomationTableRow (21 properties), AutomationWorkflowActionResponse (18 properties). Each schema is shown below with its type and property counts.
AutomationRequestSnapshot
object
Public Leadping API schema for automation request snapshot data.
14 properties
AutomationRequest
object
Defines the fields clients can send when working with automation configuration.
11 properties1 required
AutomationWorkflowEventResponse
object
User-safe workflow history event returned for lead automation status.
9 properties
AutomationPreviewActionResult
object
Result schema for the Leadping API automation preview action result returned by lookup and validation endpoints.
5 properties
OrderByOption
object
Defines one field and direction used to order an API query result set.
2 properties
PagedResultOfAutomationTableRow
object
Returns one page of query results together with page-size, optional total-count, and opaque continuation-cursor metadata.
4 properties
ProblemDetails
object
Standard problem-details response containing machine-readable and human-readable information about an HTTP API error.
5 properties
AutomationAction
object
Public Leadping API schema for automation action data.
5 properties
RequestDataOptions
object
Defines cursor pagination, sorting, search, exact-match filters, and range filters for a structured API query.
8 properties
AutomationTableRow
object
Summarizes automation data in paginated and searchable results.
21 properties
AutomationActionRunRecord
object
History record schema for Leadping API automation action run record data exposed in automation and audit views.
13 properties
RangeFilter
object
Selects records by applying inclusive or exclusive lower and upper bounds to a named comparable field.
5 properties
AutomationWorkflowActionResponse
object
User-safe action status returned for lead automation workflow visibility.
18 properties
AutomationRunRecord
object
History record schema for Leadping API automation run record data exposed in automation and audit views.
14 properties
AutomationResponse
object
Describes automation configuration data returned by Leadping.
22 properties
AutomationPreviewRequest
object
Defines the fields clients can send when working with automation preview.
2 properties1 required
AutomationPreviewConditionResult
object
Result schema for the Leadping API automation preview condition result returned by lookup and validation endpoints.
3 properties
ExactMatchFilter
object
Selects records whose named field equals a supplied scalar value.
2 properties
AutomationConsoleResponse
object
Recent persisted execution runs for an automation console.
2 properties
AutomationTrigger
object
Public Leadping API schema for automation trigger data.
5 properties
AutomationConditionGroup
object
Public Leadping API schema for automation condition group data.
3 properties
AutomationValidationResult
object
Result schema for the Leadping API automation validation result returned by lookup and validation endpoints.
2 properties
AutomationCondition
object
Public Leadping API schema for automation condition data.
5 properties
AutomationConnection
object
A directed connection between two nodes in an automation graph.
3 properties
IdNamePair
object
Provides a compact API reference to another resource using its stable identifier and human-readable display name.
2 properties2 required
AutomationWorkflowRunResponse
object
User-safe automation workflow run status returned for a lead.
27 properties
AutomationPreviewResponse
object
Describes automation preview data returned by Leadping.
6 properties
Specification
The full machine-readable OpenAPI contract behind this narrative.
Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.
Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.
MCP tools for apis
4 tools reach this content
search_api_evangelistSearch every content type across the network at once.
find_relatedThe shared-tag relevance graph — what else covers this.
get_tagEverything one tag labels, across all content types.
guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
A second provider on the same verified email joins the account you already have.
Your account
ⓘWhere this information came from
This is an independent, third-party profile of Leadping Automations 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.
