Manages phone-number discovery, purchasing, assignment, configuration, and compliance. Use these endpoints to search available numbers, manage owned numbers and caller identity, configure messaging or voice behavior, and monitor registration and warmup state.
Leadping Phone Numbers API is one of 31 APIs that Leadping publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Phone Numbers. 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 11 paths,
and defines 36 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 operations11 paths36 schemas2 DELETE3 GET8 POST1 PUT
Metadata
The identity and technical contract details declared by the specification.
Leadping Phone Numbers 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 11 paths, the API surfaces 14 operations — 2 DELETE, 3 GET, 8 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
Phone Numbers 14
Manages phone-number discovery, purchasing, assignment, configuration, and compliance. Use these endpoints to search available numbers, manage owned numbers and caller identity, c…
The contract defines 36 schemas that model the data the API accepts and returns. The most detailed are OutboundPhoneNumberCapacity (32 properties), OutgoingNumberSelectionResponse (14 properties), EligibleOutgoingNumberResponse (14 properties), PhoneNumberTableRow (13 properties). Each schema is shown below with its type and property counts.
PhoneNumberRequest
object
Defines the fields clients can send when working with phone number update.
2 properties1 required
SmsReadinessState
string
Describes whether an organization is configured and permitted to send SMS or MMS traffic through Leadping.
IdNamePair
object
User summary connected to this automation configuration response.
2 properties2 required
SmsReadinessUiState
object
Describes SMS readiness UI state data used in Leadping API requests and responses.
3 properties
PhoneNumberSearchResponse
object
Describes phone number search data returned by Leadping.
1 property
PhoneNumberSearchRequest
object
Defines the fields clients can send when working with phone number search.
2 properties
OutgoingNumberSelectionReason
string
Explains why Leadping selected, rejected, or substituted an outgoing caller or messaging number.
ExactMatchFilter
object
2 properties1 required
OrderByOption
object
2 properties1 required
PagedResultOfPhoneNumberTableRow
object
4 properties
PhoneNumberOptOutMetricsResponse
object
Describes phone number opt-out metrics data returned by Leadping.
5 properties
PhoneNumberTableRow
object
Summarizes phone number data in paginated and searchable results.
13 properties
PhoneLocationSource
object
Describes how a phone location value was resolved.
2 properties
EligibleOutgoingNumberResponse
object
Describes a Leadping phone number that is eligible to send an outbound message or place a call.
14 properties
PhoneNumberResponse
object
Describes a Leadping-managed phone number, including capabilities, messaging registration, health, and assignment details.
11 properties
SmsReadinessHealthStatus
string
Summarizes the severity of conditions affecting an organization's ability to send compliant SMS or MMS traffic.
Coordinate
object
Latitude and longitude coordinate for this lead contact profile.
2 properties2 required
RequestDataOptions
object
8 properties
PhoneNumberMessagingEventResponse
object
Describes a messaging event used to calculate delivery, failure, and opt-out metrics for a phone number.
9 properties
PhoneNumberTrafficMetricsResponse
object
Describes phone number traffic metrics data returned by Leadping.
12 properties
OutboundPhoneNumberCapacity
object
Reports the sending capacity, current load, and availability of a phone number considered for outbound delivery.
32 properties
OutgoingNumberManualOverrideRequest
object
Defines the fields clients can send when working with outgoing number manual override.
2 properties2 required
PhoneNumberTrafficTrendPoint
object
Time-series data point schema for Leadping API phone number traffic trend bucket charts and metrics.
9 properties
SmsReadinessStatusResponse
object
Describes SMS warmup status data returned by Leadping.
8 properties
PhoneNumberLocation
object
Public Leadping API schema for phone number location data.
9 properties
PhoneNumberRoutingMetadata
object
Public Leadping API schema for phone number routing metadata data.
6 properties
PhoneNumberReadiness
object
Messaging and calling warmup for a Leadping phone number.
6 properties
PhoneNumberSearchResult
object
Result schema for the Leadping API phone number search result returned by lookup and validation endpoints.
2 properties
PhoneNumberAvailabilityResponse
object
Reports whether a phone number is available for purchase or assignment and explains any blocking condition.
5 properties
PhoneNumberOutboundHealthStatus
string
Defines phone-number outbound health states used by pacing.
PhoneNumberAvailabilityRequest
object
Defines the phone number and capability requirements Leadping should verify before purchase or assignment.
1 property1 required
RangeFilter
object
5 properties1 required
OutgoingNumberSelectionResponse
object
Describes outgoing number selection data returned by Leadping.
14 properties
ProblemDetails
object
Standard problem-details response containing machine-readable and human-readable information about an HTTP API error.
7 properties
PhoneNumberStatusResponse
object
Describes a phone number's current warmup stage, limits, progress, and readiness for production traffic.
8 properties
OutgoingNumberSelectionRequest
object
Defines the fields clients can send when working with outgoing number selection.
7 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 Phone Numbers 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.
