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 Calls API

Manages outbound Leadping calls and active call-control workflows. Use these endpoints to initiate or cancel a call, retrieve call state, and transfer an active call within supported telephony flows.

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

Tagged areas include Calls. 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 4 operations across 4 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version v1.

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

4 operations 4 paths 5 schemas 1 GET3 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 Calls 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 4

Across 4 paths, the API surfaces 4 operations — 1 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Calls 4

Manages outbound Leadping calls and active call-control workflows. Use these endpoints to initiate or cancel a call, retrieve call state, and transfer an active call within suppor…

POST
/phone-call/initiate
Initiate a Leadping phone call
Calls_InitiateCall body → 200400401403429
POST
/phone-call/{callId}/hangup
End an active Leadping phone call
Calls_HangupCall 1 param → 200400404401403429
GET
/phone-call/{callId}/status
Get the status of a Leadping phone call
Calls_GetCallStatus 1 param → 200400401403429
POST
/phone-call/{callId}/transfer
Transfer an active Leadping phone call
Calls_TransferCall 2 params → 200400404401403429

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are PhoneCallResponse (26 properties), InitiateCallRequest (7 properties), ProblemDetails (5 properties), CommunicationConsoleEntry (5 properties). Each schema is shown below with its type and property counts.

CommunicationConsoleEntry
object
Describes one durable diagnostic entry from the processing of a communication.
5 properties
PhoneCallResponse
object
Describes a Leadping phone call, including participants, direction, provider state, timing, recording, and billing details.
26 properties
InitiateCallRequest
object
Defines the fields clients can send when working with phone call initiation.
7 properties 1 required
ProblemDetails
object
Standard problem-details response containing machine-readable and human-readable information about an HTTP API error.
5 properties
PhoneCallStatus
string
Describes the durable business outcome of a Leadping phone call after provider status normalization.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

leadping-calls-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 Contact API
Leadping Conversations API
Leadping Events 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 Calls 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.