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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Leadping

Leadping Phone Numbers API

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.

Documentation Provider Profile APIs.io OpenAPI GitHub

Leadping Phone Numbers API is one of 29 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 operations 11 paths 36 schemas 2 DELETE3 GET8 POST1 PUT

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
Contact
Leadping Support
License
MIT
Terms of Service
View terms
Resource Areas
1

Authentication & Security 2

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.

PhoneNumbers 14

Manages phone-number discovery, purchasing, assignment, configuration, and compliance. Use these endpoints to search available numbers, manage owned numbers and caller identity, c…

POST
/phone-numbers/search
Search purchasable organization phone numbers
PhoneNumbers_Search body → 400500200401403429
POST
/phone-numbers/all/organization
List current-organization phone numbers
PhoneNumbers_GetAllForCurrentOrganization body → 200400401403429
POST
/phone-numbers/outgoing/conversation/{conversationId}
Select conversation sender number
PhoneNumbers_GetOutgoingForConversation 1 param body → 200400401403429
POST
/phone-numbers/outgoing/new
Select new lead sender number
PhoneNumbers_GetOutgoingForNewOutbound body → 200400401403429
POST
/phone-numbers/outgoing/manual-override
Validate sender number override
PhoneNumbers_ValidateManualOverride body → 200400401403429
POST
/phone-numbers/outgoing/conversation/{conversationId}/override
Set sender number override
PhoneNumbers_SetConversationOverride 1 param body → 200400401403429
DELETE
/phone-numbers/outgoing/conversation/{conversationId}/override
Clear sender number override
PhoneNumbers_ClearConversationOverride 1 param → 200400401403429
GET
/phone-numbers/{phoneNumberId}
Get organization phone number details by ID
PhoneNumbers_Get 1 param → 200404401403429
PUT
/phone-numbers/{phoneNumberId}
Update organization phone number settings
PhoneNumbers_Update 1 param body → 200400404500401403429
DELETE
/phone-numbers/{phoneNumberId}
Delete an organization phone number by ID
PhoneNumbers_Delete 1 param → 204400404500401403429
POST
/phone-numbers
Create an organization phone number for messaging
PhoneNumbers_Create body → 200400500401403429
GET
/phone-numbers/{phoneNumber}/status
Get organization phone number provider status
PhoneNumbers_GetStatus 4 params → 200400500401403429
GET
/phone-numbers/{phoneNumberId}/warmup
Get organization phone number warmup status
PhoneNumbers_GetWarmupStatus 4 params → 200400401403429
POST
/phone-numbers/is-available-for-purchase
Check phone number purchase availability
PhoneNumbers_IsAvailableForPurchase body → 200400500401403429

Schemas 36

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.

OutboundPhoneNumberCapacity
object
Reports the sending capacity, current load, and availability of a phone number considered for outbound delivery.
32 properties
PhoneNumberRoutingMetadata
object
Public Leadping API schema for phone number routing metadata data.
6 properties
PhoneNumberOutboundHealthStatus
string
Defines phone-number outbound health states used by pacing.
PagedResultOfPhoneNumberTableRow
object
Returns one page of query results together with page-size, optional total-count, and opaque continuation-cursor metadata.
4 properties
PhoneNumberReadiness
object
Messaging and calling warmup for a Leadping phone number.
6 properties
PhoneNumberTrafficMetricsResponse
object
Describes phone number traffic metrics data returned by Leadping.
12 properties
Coordinate
object
Latitude and longitude coordinate for this lead contact profile.
2 properties 2 required
PhoneNumberRequest
object
Defines the fields clients can send when working with phone number update.
5 properties 2 required
PhoneNumberAvailabilityResponse
object
Reports whether a phone number is available for purchase or assignment and explains any blocking condition.
5 properties
OrderByOption
object
Defines one field and direction used to order an API query result set.
2 properties
ProblemDetails
object
Standard problem-details response containing machine-readable and human-readable information about an HTTP API error.
5 properties
PhoneNumberSearchResult
object
Result schema for the Leadping API phone number search result returned by lookup and validation endpoints.
2 properties
PhoneNumberMessagingEventResponse
object
Describes a messaging event used to calculate delivery, failure, and opt-out metrics for a phone number.
9 properties
RequestDataOptions
object
Defines cursor pagination, sorting, search, exact-match filters, and range filters for a structured API query.
8 properties
PhoneNumberOptOutMetricsResponse
object
Describes phone number opt-out metrics data returned by Leadping.
5 properties
OutgoingNumberSelectionResponse
object
Describes outgoing number selection data returned by Leadping.
14 properties
PhoneNumberTrafficTrendPoint
object
Time-series data point schema for Leadping API phone number traffic trend bucket charts and metrics.
9 properties
OutgoingNumberSelectionReason
string
Explains why Leadping selected, rejected, or substituted an outgoing caller or messaging number.
RangeFilter
object
Selects records by applying inclusive or exclusive lower and upper bounds to a named comparable field.
5 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.
PhoneNumberLocation
object
Public Leadping API schema for phone number location data.
9 properties
EligibleOutgoingNumberResponse
object
Describes a Leadping phone number that is eligible to send an outbound message or place a call.
14 properties
ExactMatchFilter
object
Selects records whose named field equals a supplied scalar value.
2 properties
PhoneLocationSource
object
Describes how a phone location value was resolved.
2 properties
SmsReadinessUiState
object
Describes SMS readiness UI state data used in Leadping API requests and responses.
3 properties
PhoneNumberStatusResponse
object
Describes a phone number's current warmup stage, limits, progress, and readiness for production traffic.
8 properties
PhoneNumberSearchRequest
object
Defines the fields clients can send when working with phone number search.
2 properties
OutgoingNumberSelectionRequest
object
Defines the fields clients can send when working with outgoing number selection.
7 properties
SmsReadinessStatusResponse
object
Describes SMS warmup status data returned by Leadping.
8 properties
IdNamePair
object
Provides a compact API reference to another resource using its stable identifier and human-readable display name.
2 properties 2 required
OutgoingNumberManualOverrideRequest
object
Defines the fields clients can send when working with outgoing number manual override.
2 properties 2 required
PhoneNumberTableRow
object
Summarizes phone number data in paginated and searchable results.
13 properties
SmsReadinessState
string
Describes whether an organization is configured and permitted to send SMS or MMS traffic through Leadping.
PhoneNumberSearchResponse
object
Describes phone number search data returned by Leadping.
1 property
PhoneNumberAvailabilityRequest
object
Defines the phone number and capability requirements Leadping should verify before purchase or assignment.
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

leadping-phonenumbers-api-openapi.yml Raw ↑

Other APIs Leadping publishes across the network.

Leadping MCP Servers
AE Profile APIs.io
Leadping Webhook Events
AE Profile APIs.io
Leadping Analytics API
AE Profile APIs.io
Leadping Automations API
AE Profile APIs.io
Leadping Call Events API
AE Profile APIs.io
Leadping Calls API
AE Profile APIs.io
Leadping Contact API
AE Profile APIs.io
Leadping Conversations API
AE Profile APIs.io
Leadping Events API
AE Profile APIs.io
Leadping Feedback API
AE Profile APIs.io
Leadping Leads API
AE Profile APIs.io
Leadping Lead Status Changes API
AE Profile APIs.io
#Phone Numbers
← Back to L APIs
API Details
ID
leadping:leadping-phonenumbers-api
Base URL
https://api.leadping.ai
Docs
https://leadping.ai/docs/api-reference
Provider
Leadping
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

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.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=leadping-phonenumbers-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/leadping-phonenumbers-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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.