Manages lead intake, records, assignment, routing, and lifecycle operations. Use these endpoints to ingest leads from trusted sources, search and update lead records, manage ownership and tags, and archive or delete leads.
Leadping Leads API is one of 31 APIs that Leadping publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Leads. 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
14 operations
across 10 paths,
and defines 43 schemas.
It is described by OpenAPI 3.2.0, at version v1.
Requests are made against a single base URL, https://api.leadping.ai.
14 operations10 paths43 schemas2 DELETE3 GET6 POST3 PUT
Metadata
The identity and technical contract details declared by the specification.
Leadping Leads 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 14
Across 10 paths, the API surfaces 14 operations — 2 DELETE, 3 GET, 6 POST, 3 PUT. Each is listed below with its method, path, parameters, and response codes.
Leads 14
Manages lead intake, records, assignment, routing, and lifecycle operations. Use these endpoints to ingest leads from trusted sources, search and update lead records, manage owner…
Assign an organization lead to an active member, or return it to the unassigned…
Leads_Assign1 parambody→ 200400403404401429
Schemas 43
The contract defines 43 schemas that model the data the API accepts and returns. The most detailed are LeadMetadata (35 properties), LeadIntakeRequest (33 properties), AutomationWorkflowRunResponse (27 properties), LeadTableRow (26 properties). Each schema is shown below with its type and property counts.
IdNamePair
object
User summary connected to this automation configuration response.
2 properties2 required
LeadArchiveRequest
object
Defines the fields clients can send when working with lead archive.
2 properties
PhoneIdentityResponse
object
Describes Leadping's canonical identity for a phone number, including normalization, carrier, line type, reputation, and lookup history.
9 properties
LeadTagsRequest
object
Defines the fields clients can send when working with lead tag update.
3 properties2 required
CurrentLeadStatusSummary
object
Summary schema for Leadping API current lead status change summary data used in dashboards and reports.
8 properties
StreetAddress
object
Postal street address for the lead contact profile.
9 properties
PhoneIdentityLookupAction
object
An auditable lookup, enrichment, or reputation check performed for a phone identity.
7 properties
AutomationWorkflowStatusResponse
object
Automation workflow status collection for a lead.
2 properties
ExactMatchFilter
object
2 properties1 required
AutomationWorkflowRunResponse
object
User-safe automation workflow run status returned for a lead.
27 properties
Phone
object
Public Leadping API schema for lead phone number data.
3 properties
OrderByOption
object
2 properties1 required
PhoneLookupPortability
object
Number-portability and routing data returned by Telnyx.
13 properties
PhoneLocationSource
object
Describes how a phone location value was resolved.
2 properties
LeadAssignmentRequest
object
Assigns an organization lead to an active organization member. A null user ID returns the lead to the unassigned queue.
1 property
LeadResponse
object
Describes lead data returned by Leadping.
22 properties
Coordinate
object
Latitude and longitude coordinate for this lead contact profile.
2 properties2 required
RequestDataOptions
object
8 properties
PhoneLookup
object
Public Leadping API schema for phone lookup result data.
13 properties
PhoneLookupProviderSnapshot
object
Lossless provider snapshot retained with a phone identity for replay, audits, and fields added by providers later.
5 properties
PhoneIdentityLookupActionStatus
string
Identifies the outcome of a phone identity lookup action.
LeadRequest
object
Defines the fields clients can send when working with lead.
7 properties5 required
TagSummary
object
Summary schema for Leadping API tag summary data used in dashboards and reports.
4 properties
AutomationWorkflowActionResponse
object
User-safe action status returned for lead automation workflow visibility.
18 properties
PhoneLookupCallerName
object
Caller-name data returned by the phone lookup provider.
2 properties
PhoneNumberLocation
object
Public Leadping API schema for phone number location data.
9 properties
LeadTableRow
object
Summarizes lead data in paginated and searchable results.
26 properties
PagedResultOfLeadTableRow
object
4 properties
LeadProfile
object
Public Leadping API schema for lead demographic profile data.
13 properties
PhoneIdentityLookupActionType
string
Identifies the kind of lookup action performed for a phone identity.
LeadContact
object
Public Leadping API schema for lead contact profile data.
8 properties
RangeFilter
object
5 properties1 required
AutomationWorkflowEventResponse
object
User-safe workflow history event returned for lead automation status.
9 properties
LeadMetadata
object
Public Leadping API schema for lead attribution metadata data.
35 properties1 required
ProblemDetails
object
Standard problem-details response containing machine-readable and human-readable information about an HTTP API error.
7 properties
LeadIntakeRequest
object
Defines the fields clients can send when working with lead intake.
33 properties
LeadArchiveReason
integer
Defines why a lead was removed from the active working pipeline.
PhoneLookupCarrier
object
Complete carrier metadata returned by a phone number lookup provider.
6 properties
LeadResponse_2
object
Describes lead data returned by Leadping.
20 properties
PhoneIdentityResponse_2
object
Describes Leadping's canonical identity for a phone number, including normalization, carrier, line type, reputation, and lookup history.
9 properties
PhoneLookup_2
object
Public Leadping API schema for phone lookup result data.
13 properties
ProblemDetails_2
object
Standard problem-details response containing machine-readable and human-readable information about an HTTP API error.
5 properties
PhoneLookupCarrier_2
object
Complete carrier metadata returned by a phone number lookup provider.
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 Leads 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.
