Leadping website screenshot

Leadping

Leadping is a lead-management and responsible-outreach platform for teams that need to move a new inbound lead from source to first touch without stitching together separate tools. It captures leads from approved sources, routes and assigns them, runs follow-up automations, sends SMS and MMS, places and transfers calls, keeps conversation and event history together, enforces recipient suppression and opt-out handling, tracks A2P 10DLC carrier registration and phone-number warmup, requires TrustedForm consent evidence where a source needs it, and reports usage, billing and analytics. The 137-operation REST API is published as an OpenAPI 3.1.1 contract with six Kiota-generated first-party SDKs, two remote MCP servers, Standard Webhooks signing, and an unusually complete machine-readable discovery surface including APIs.json, an RFC 9727 API catalog, RFC 9728 protected-resource metadata, llms.txt and an agent-skill index.

Leadping publishes 31 API contracts indexed on the APIs.io network, including Analytics API, Automations API, Call Events API, and 28 more. Tagged areas include Lead Management, Sales & marketing automation, SMS Messaging, A2P 10DLC, and CPaaS.

The Leadping catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

Leadping’s developer surface includes documentation, API reference, getting-started guide, support, pricing, signup flow, changelog, and 43 more developer resources.

🌐 Visit website📡 Profile data on GitHub
82.1/100 exemplar ▬ flat Agent 72/100 agent ready Front door AI 1/6 silent Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →
AccessPaid
Agents Publishes an API Onboarding Descriptor (AOD 0.1)
1 published contract 2 MCP Servers 4 Agent Skills
Lead ManagementSales & marketing automationSMS MessagingA2P 10DLCCPaaSCommunicationsVoice/callingCompliance & consentAgent-NativeMCPLead intakeConversationsAutomationSuppression & opt-outWebhookA2A

What this lets a business do 5

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Application Communications
AE-150
CallsPhone NumbersSMSSmsEvents
POST /sms/send POST /sms/media POST /events/sms/phone/{phoneNumber} POST /phone-numbers/search
Sales Management
BC-410
Lead StatusesLeadStatusChangesLeads
POST /leads PUT /leads/{id} PUT /leads/{leadId}/status GET /leads/{leadId}/status-history
Subscription Billing & Revenue Management
BC-4250
PaymentMethodsUsage
POST /usage/all/my GET /payment-methods/invoices POST /payment-methods/{id}/default
Marketing Management
BC-400
BlogArticles
GET /blog
Customer Relationship Management
BC-420
Tags
GET /tags

What people ask Leadping 29

The questions people put to an LLM, and the jobs they hand an agent, that Leadping's APIs answer — each one linked to the operation that does it. Generated by API Evangelist

Leadping Organizations API Get my organization profile “What settings does my current organization have?” Create a new organization “How do I start a brand new organization account and become its owner?” Update my organization profile “How do I change my organization's name or website?” List organizations I can switch to “Which organizations do I belong to?”
Leadping Leads API Create a lead from an external source “How do I push a lead captured on another system into Leadping with structured contact data?” Create a lead from a flat intake payload “How do I send a lead as a flat JSON intake body?” Create a lead from query-string intake “Can I post a lead just by putting its fields in a URL query string?” Get a lead “How do I pull up everything about one lead?”
Leadping Phone Numbers API Search phone numbers to buy “What phone numbers are available to purchase in my area?” List my organization's phone numbers “Which phone numbers does my organization own?” Pick the sender number for a conversation “Which of my numbers will be used to reply in an existing conversation?” Pick the sender number for a new lead “Which number will be used when I text a new lead for the first time?”
Leadping Automations API Create a lead follow-up automation “How do I set up an automation that follows up with new leads?” Update a follow-up automation “How do I change the triggers on an existing automation?” Get a follow-up automation “Which triggers and message steps does this automation use?” Delete a follow-up automation “How do I permanently remove an automation so it stops scheduling follow-ups?”
Leadping Notifications API Get a notification “How do I open one notification and see its content?” List my notifications “What alerts and updates have I received?” Count unread notifications “How many unread notifications do I have?” Mark a notification as read “How do I mark one notification as read?”
Leadping Events API List my lead events “What lead, SMS, call and automation events can I see?” List an organization's event history “How can an admin review every event across an organization?” List a conversation's events “What notes, messages and calls happened in one conversation?” List a lead's event history “What has happened with a lead across routing, automation and messaging?”
Leadping Lead Status Changes API Set a lead's current status “How do I record an outcome like appointment set on a lead?” Edit a status history entry “Can I fix a status change that was logged with the wrong outcome?” Get a status history entry “How do I look at a single past status change and its notes?” Delete a status history entry “How do I remove an outcome record that shouldn't show in reports?”
Leadping Sources API Create a lead intake source “How do I set up a new lead source for a vendor sending me leads?” Update a lead source “How do I change which states an existing source accepts?” Get a lead source “How do I check the intake settings of one lead source?” Delete a lead source “How do I stop a source from sending me any more leads?”
Leadping Users API Get my default payment method “Which card is my default for billing?” Get my user profile “What does my Leadping user profile contain?” Update my user profile “How do I change my name or phone on my profile?” Update my notification preferences “How do I get texted when a new lead comes in?”
Leadping Payment Methods API List payment methods “What payment methods does my organization have on file?” List invoices “Where can I see my past invoices and whether they were paid?” Get a link to an invoice PDF “How do I download a PDF copy of an invoice?” Get a payment method “How do I see the card details of one payment method?”
Leadping Suppressions API Block a recipient from outreach “How do I stop contacting someone who asked to opt out?” Release a recipient suppression “How do I allow a previously opted-out contact to be messaged again?” Check if a recipient is suppressed “Am I allowed to text this phone number, or is it suppressed?” List suppressed recipients “Who is on my organization's do-not-contact list?”
Leadping Lead Statuses API List lead statuses “What lead statuses has my organization defined?” Create a lead status “How do I add a new pipeline stage for leads?” Update a lead status “How do I rename an existing pipeline stage?” Archive a lead status “How do I retire a pipeline stage without losing lead history?”

Showing 12 of 29 APIs with phrasing — see every API.

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0
Composite quality — 82.1/100 · exemplar
Contract Quality 13.0 / 19
Developer Ergonomics 11.0 / 15
Access Clarity 15.0 / 15
Operational Transparency 7.4 / 10
Contract Governance 4.1 / 9
Discoverability 6.4 / 8
Regulatory Posture 7.2 / 15
Create-or-Update Ergonomics 2.8 / 10
Agent readiness — 72/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 10 / 10
Documented Reversibility 6 / 6
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 9 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 7 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 6 / 6
Agent Skills 5 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 8 / 8
Dry-Run / Simulate Mode 4 / 4
Delegated User Identity 6 / 6
Protected Resource Metadata 5 / 5
Registration Without a Human 0 / 6
Agentic Commerce Well-Known Document 0 / 5
Pagination 0 / 5
Distinct Operations 3 / 3
MCP Tool Quality 6 / 6
Regulatory Posture applies to this provider. Its tags matched the Telecommunications regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site. Kin Score badge preview for Leadping It updates itself when the score changes. Paste this where you link to your API docs: 
<a href="https://apis.io/providers/leadping/"><img src="https://apis.io/badge/leadping/card.svg" alt="Leadping on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
  • Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
  • Pagination +5 pts — share of collection GETs (an array, or one wrapped in data/items/results ...) that declare a page/limit/offset/cursor parameter, a Link header or a next/cursor field; na with no collection GETs
  • Agentic Commerce Well-Known Document +5 pts — a parsing /.well-known/ucp.json or acp.json declaring a version and at least one service, OR (0.27) a live x402 payment challenge from _data/x402-adoption.json — `self` when its endpoints are on the provider's own domain, `platform` when they are on a vendor's
  • Consent & Bot Identity +3 pts — common[].type includes AIPREF, ContentSignal, WebBotAuth, or HTTPMessageSignatures
Kin Score — facets with the most composite points still available (weight × headroom):
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/leadping/apis.yml: open an issue on github.com/api-evangelist/leadping to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

MarketPositionDepthRegistered MCP serverDeclares compatibility
Pipedrive Marketplace (CRM integrations from third-party publishers for the SMB sales CRM) distribution 28.7 - 1
Official SDKs on Packagist, pub.dev and Hex distribution 28.7 - 1

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 5

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Agent2Agent
measured — observed by APIs.io (conformant)
Model Context Protocol (MCP)
measured — observed by APIs.io (documented)
OAuth 2.0 Protected Resource Metadata
measured — observed by APIs.io (verified)
OpenAPI
measured — observed by APIs.io (published)
OAuth 2.0
measured — observed by APIs.io (declared)

APIs 31

Individual APIs this provider publishes, each with its own machine-readable definition.

Leadping MCP Servers

Two remote Model Context Protocol servers. A public read-only documentation server at https://leadping.ai/docs/mcp answers anonymous tools/list with search, virtual-filesystem a...

Leadping Webhook Events

Outbound HTTPS webhook deliveries fired by Leadping automations, signed with the Standard Webhooks specification (HMAC-SHA256 over {webhook-id}.{webhook-timestamp}.{body}, whsec...

Leadping Analytics API

Provides lead, communication, conversion, and organization performance analytics. Use these endpoints to measure activity over time, compare outcomes, and power operational dash...

Leadping Automations API

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...

Leadping Call Events API

Provides call event records for auditing, diagnostics, and reporting. Use these endpoints to search and inspect lifecycle events emitted as Leadping calls are initiated, connect...

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 supp...

Leadping Contact API

Accepts public contact and website inquiry submissions for Leadping. Use these endpoints to send a structured support or sales inquiry from an application or submit the Leadping...

Leadping Conversations API

Provides lead conversation timelines and inbox-oriented conversation views. Use these endpoints to list recent conversations and retrieve the cross-channel communication history...

Leadping Events API

Provides a unified record of Leadping activity across communication channels. Use these endpoints to retrieve event timelines, search event history, inspect event details, and r...

Leadping Feedback API

Captures Leadping product feedback and supports administrative triage. Users can submit feedback, while authorized staff can search, inspect, classify, and update feedback throu...

Leadping Leads API

Manages lead intake, records, assignment, routing, and lifecycle operations. Use these endpoints to ingest leads from trusted sources, search and update lead records, manage own...

Leadping Lead Status Changes API

Manages the auditable history of lead status transitions. Use these endpoints to change a lead's status, correct transition records, search status history, and export status act...

Leadping Notifications API

Manages user notifications, announcements, and push-notification installations. Use these endpoints to retrieve notification feeds and unread counts, update read state, and regi...

Leadping Organizations API

Manages Leadping organizations, memberships, invitations, settings, and API credentials. Use these endpoints to maintain organization profiles and branding, manage members and i...

Leadping Outbound Delivery API

Reports outbound delivery pacing and sending capacity for the current organization. Use these endpoints to determine whether outbound communications can proceed and to understan...

Leadping Sms API

Sends and manages SMS and MMS communications through Leadping. Use these endpoints to send messages, upload MMS media, and cancel eligible scheduled messages while preserving co...

Leadping Sms Events API

Provides SMS and MMS event records for delivery tracking and diagnostics. Use these endpoints to search and inspect message lifecycle events, including outbound delivery updates...

Leadping Sources API

Manages lead sources, intake credentials, routing defaults, and attribution. Use these endpoints to create and configure sources, search source records, inspect source activity,...

Leadping Suppressions API

Manages recipient suppression state for compliant Leadping communication workflows. Use these endpoints to check contact eligibility, record or release suppressions, and review ...

Leadping Tags API

Manages organization-defined tags for categorizing and routing leads. Use these endpoints to list, create, update, and archive reusable tags that support lead filtering, automat...

Leadping Telephony API

Provides shared authentication and bootstrap data for Leadping telephony clients. Use this endpoint to obtain the scoped credentials and configuration required to initialize sup...

Leadping Transactions API

Provides organization wallet and billing transaction records. Use these endpoints to search transaction history, inspect individual charges or credits, review transaction summar...

Leadping Usage API

Provides billable usage records for Leadping services. Use these endpoints to review messaging and calling consumption, inspect usage summaries, and reconcile provider activity ...

Leadping User Data Exports API

Creates and delivers user-requested exports of Leadping account data. Use these endpoints to request an export, monitor its preparation status, and download the completed archiv...

Leadping Users API

Manages the current Leadping user's profile, preferences, setup, and account workflows. Use these endpoints to retrieve and update user data, configure communication and complia...

Leadping Wallets API

Manages organization wallet balances, funding, and credit activity. Use these endpoints to inspect wallet state and history, configure wallet behavior, add funds, and record cre...

Leadping Blog Articles API

Provides published Leadping blog content. Use these endpoints to list published articles and retrieve an individual article by its public slug.

Leadping Leadping API

The Leadping API API from Leadping — 2 operation(s) for leadping api.

Leadping Lead Statuses API

Manages the lead statuses used to classify and track leads throughout their lifecycle. Use these endpoints to list, create, update, and archive organization-specific lead status...

Leadping Payment Methods API

Manages organization payment methods and billing invoices. Use these endpoints to add, confirm, inspect, and remove payment methods or retrieve invoices associated with the curr...

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,...

Scroll for all 31

MCP Servers 2

Model Context Protocol servers that expose these APIs to AI agents.

Leadping MCP Server

Leadping operates TWO remote MCP servers: a public read-only documentation server at https://leadping.ai/docs/mcp (Mintlify-hosted, anonymous tools/list succeeds) and an authent...

MCP SERVER

Leadping MCP Server

MCP SERVER

Agent Skills 4

Packaged agent skills for driving this provider's APIs from an AI assistant.

leadping-first-response-sms

AGENT SKILL

leadping-lead-intake

AGENT SKILL

leadping-lead-lifecycle

AGENT SKILL

leadping-suppression-optout

AGENT SKILL

Leadping API pricing

Prices published by Leadping, read 2026-10-28 from leadping.ai/pricing.

PlanPrice
Monthly $60.00/ month
Includes: $5.00 starting usage credit; full platform including API access
Annual $50.00/ month
Includes: Billed once a year at $600.00 . $20.00 starting usage credit
SMS segment $0.02
Outbound MMS $0.06
Voice minute $0.021
Phone number $2.00/ mo
Number health / number (optional) $2.00/ mo
Texting approval application $40.00

All 9 plans, limits and sources →

Billed by: workspace · FinOps profile →

Pricing Plans 2

Published pricing tiers and plan structures.

Leadping Plans Pricing

9 plans

PLANS

Leadping Price Estimates

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Leadping Rate Limits

4 limits

RATE LIMITS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Leadping

SLA

FinOps 1

Cost, billing, and metering signals for API financial operations.

Leadping Finops

FINOPS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Leadping Webhooks

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Leadping API Rules

80 rules · 57 errors 19 warnings 4 info

SPECTRAL

OpenAPI Overlays 30

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Leadping Analytics Api Phrasing Overlay

2 actions · phrasing · leadping-analytics-api-openapi.yml

GENERATED

Leadping Api Overlay

9 actions · update · leadping-openapi.json

DERIVED

Leadping Automations Api Phrasing Overlay

10 actions · phrasing · leadping-automations-api-openapi.yml

GENERATED

Leadping Blogarticles Api Phrasing Overlay

3 actions · phrasing · leadping-blogarticles-api-openapi.yml

GENERATED

Leadping Callevents Api Phrasing Overlay

5 actions · phrasing · leadping-callevents-api-openapi.yml

GENERATED

Leadping Calls Api Phrasing Overlay

5 actions · phrasing · leadping-calls-api-openapi.yml

GENERATED

Leadping Contact Api Phrasing Overlay

3 actions · phrasing · leadping-contact-api-openapi.yml

GENERATED

Leadping Conversations Api Phrasing Overlay

4 actions · phrasing · leadping-conversations-api-openapi.yml

GENERATED

Leadping Events Api Phrasing Overlay

8 actions · phrasing · leadping-events-api-openapi.yml

GENERATED

Leadping Feedback Api Phrasing Overlay

2 actions · phrasing · leadping-feedback-api-openapi.yml

GENERATED

Leadping Lead Statuses Api Phrasing Overlay

5 actions · phrasing · leadping-lead-statuses-api-openapi.yml

GENERATED

Leadping Leadping Api Api Phrasing Overlay

3 actions · phrasing · leadping-leadping-api-api-openapi.yml

GENERATED

Leadping Leads Api Phrasing Overlay

15 actions · phrasing · leadping-leads-api-openapi.yml

GENERATED

Leadping Leadstatuschanges Api Phrasing Overlay

8 actions · phrasing · leadping-leadstatuschanges-api-openapi.yml

GENERATED

Leadping Notifications Api Phrasing Overlay

9 actions · phrasing · leadping-notifications-api-openapi.yml

GENERATED

Leadping Organizations Api Phrasing Overlay

22 actions · phrasing · leadping-organizations-api-openapi.yml

GENERATED

Leadping Outbounddelivery Api Phrasing Overlay

2 actions · phrasing · leadping-outbounddelivery-api-openapi.yml

GENERATED

Leadping Payment Methods Api Phrasing Overlay

7 actions · phrasing · leadping-payment-methods-api-openapi.yml

GENERATED

Leadping Phone Numbers Api Phrasing Overlay

15 actions · phrasing · leadping-phone-numbers-api-openapi.yml

GENERATED

Leadping Sms Api Phrasing Overlay

4 actions · phrasing · leadping-sms-api-openapi.yml

GENERATED

Leadping Smsevents Api Phrasing Overlay

5 actions · phrasing · leadping-smsevents-api-openapi.yml

GENERATED

Leadping Sources Api Phrasing Overlay

8 actions · phrasing · leadping-sources-api-openapi.yml

GENERATED

Leadping Suppressions Api Phrasing Overlay

6 actions · phrasing · leadping-suppressions-api-openapi.yml

GENERATED

Leadping Tags Api Phrasing Overlay

5 actions · phrasing · leadping-tags-api-openapi.yml

GENERATED

Leadping Telephony Api Phrasing Overlay

2 actions · phrasing · leadping-telephony-api-openapi.yml

GENERATED

Leadping Transactions Api Phrasing Overlay

3 actions · phrasing · leadping-transactions-api-openapi.yml

GENERATED

Leadping Usage Api Phrasing Overlay

3 actions · phrasing · leadping-usage-api-openapi.yml

GENERATED

Leadping Userdataexports Api Phrasing Overlay

4 actions · phrasing · leadping-userdataexports-api-openapi.yml

GENERATED

Leadping Users Api Phrasing Overlay

7 actions · phrasing · leadping-users-api-openapi.yml

GENERATED

Leadping Wallets Api Phrasing Overlay

3 actions · phrasing · leadping-wallets-api-openapi.yml

GENERATED

Scroll for all 30

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Leadping Authentication

http/oauth2 · 2 schemes

SECURITY

Leadping Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Leadping Vulnerability Disclosure

Hackerone · security.txt · contact published

SECURITY

Leadping Trust Center

trust center published

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Leadping Scopes

4 scopes

4 scopes

SCOPES

Resources

Get Started 5

Portal, sign-up, and the first successful call

DeveloperPortal
DeveloperPortal
 GettingStarted
GettingStarted
 SignUp
SignUp
 Sandbox
Sandbox
 Console
Console

Documentation 2

Reference material describing how the API behaves

Documentation
Documentation
 APIReference
APIReference

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

MCPServer
MCPServer
 AgentSkill
AgentSkill
 LLMsTxt
LLMsTxt
 LLMsTxt
LLMsTxt
 WellKnown
WellKnown

Design & Contract 8

Pagination, idempotency, versioning, errors, and events

Lifecycle
Lifecycle
 Conventions
Conventions
 Idempotency
Idempotency
 ErrorCatalog
ErrorCatalog
 DataModel
DataModel
 Vocabulary
Vocabulary
 Webhooks
Webhooks
 Conformance
Conformance

Scroll for all 8

Build 5

SDKs, sample code, and the tooling you integrate with

GitHubOrganization
GitHubOrganization
 Packages
Packages
 SDKs
SDKs
 SDKs
SDKs
 ToolCrosswalk
ToolCrosswalk

Access & Security 8

Authentication, authorization, and security posture

Authentication
Authentication
 SecurityTxt
SecurityTxt
 Security
Security
 VulnerabilityDisclosure
VulnerabilityDisclosure
 DomainSecurity
DomainSecurity
 TrustCenter
TrustCenter
 Compliance
Compliance
 OAuthScopes
OAuthScopes

Scroll for all 8

Operate 5

Status, limits, changes, and where to get help

Support
Support
 StatusPage
StatusPage
 ChangeLog
ChangeLog
 ChangeLog
ChangeLog
 RateLimits
RateLimits

Commercial 5

Pricing, plans, and the legal terms of use

Pricing
Pricing
 TermsOfService
TermsOfService
 PrivacyPolicy
PrivacyPolicy
 Plans
Plans
 FinOps
FinOps

Company 2

The organization behind the API

Website
Website
 Blog
Blog

Other 5

Properties that don't map to a standard resource type

CapabilityMap
CapabilityMap
 APICatalog
APICatalog
 Overlay
Overlay
 APIsJSON
APIsJSON
 AgentCard
AgentCard

Source (apis.yml)

apis.yml Raw ↑ 
aid: leadping
name: Leadping
description: Leadping is a lead-management and responsible-outreach platform for teams that need to move a new inbound lead
  from source to first touch without stitching together separate tools. It captures leads from approved sources, routes and
  assigns them, runs follow-up automations, sends SMS and MMS, places and transfers calls, keeps conversation and event history
  together, enforces recipient suppression and opt-out handling, tracks A2P 10DLC carrier registration and phone-number warmup,
  requires TrustedForm consent evidence where a source needs it, and reports usage, billing and analytics. The 137-operation
  REST API is published as an OpenAPI 3.1.1 contract with six Kiota-generated first-party SDKs, two remote MCP servers, Standard
  Webhooks signing, and an unusually complete machine-readable discovery surface including APIs.json, an RFC 9727 API catalog,
  RFC 9728 protected-resource metadata, llms.txt and an agent-skill index.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: high
  source:
  - plans
  - authentication
  - scopes
  - rate-limits
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://leadping.ai/img/favicon/leadpinglogo1024x1024.png
url: https://leadping.apievangelist.com/apis.yml
created: '2026-08-18'
modified: '2026-09-03'
specificationVersion: '0.23'
tags:
- Lead Management
- Sales & marketing automation
- SMS Messaging
- A2P 10DLC
- CPaaS
- Communications
- Voice/calling
- Compliance & consent
- Agent-Native
- MCP
- Lead intake
- Conversations
- Automation
- Suppression & opt-out
- Webhook
- A2A
tags_raw:
- Lead management
- Sales & marketing automation
- SMS/messaging
- A2P 10DLC
- CPaaS
- Communications
- Voice/calling
- Compliance & consent
- Agent-native
- MCP
- Lead intake
- Conversations
- Automations
- Suppression & opt-out
- Webhooks
- agent-native
- A2A
apis:
- name: Leadping MCP Servers
  description: Two remote Model Context Protocol servers. A public read-only documentation server at https://leadping.ai/docs/mcp
    answers anonymous tools/list with search, virtual-filesystem and feedback tools. An authenticated organization-tools server
    at https://api.leadping.ai/mcp exposes read and lead-management tools over stateless Streamable HTTP at MCP protocol revision
    2026-07-28, using a Leadping user access token or an organization API key.
  humanURL: https://leadping.ai/docs/mcp-server
  baseURL: https://api.leadping.ai/mcp
  tags:
  - MCP
  - Agent-Native
  - Lead Management
  tags_raw:
  - MCP
  - Agent-native
  - Lead management
  - agent-native
  properties:
  - type: MCPServer
    url: mcp/leadping-mcp.yml
  - type: MCPServer
    url: https://api.leadping.ai/mcp
  - type: MCPServer
    url: https://leadping.ai/docs/mcp
  - type: ToolCrosswalk
    url: mcp/leadping-tool-crosswalk.yml
  - type: Documentation
    url: https://leadping.ai/docs/mcp-server
  - type: Authentication
    url: https://leadping.ai/auth.md
- name: Leadping Webhook Events
  description: Outbound HTTPS webhook deliveries fired by Leadping automations, signed with the Standard Webhooks specification
    (HMAC-SHA256 over {webhook-id}.{webhook-timestamp}.{body}, whsec_ signing secret). Leadping publishes no AsyncAPI document
    and no event-type catalog; the verification contract is documented in prose only.
  humanURL: https://leadping.ai/docs/validating-webhooks
  baseURL: https://api.leadping.ai
  tags:
  - Webhook
  - Communications
  - Automation
  tags_raw:
  - Webhooks
  - Communications
  - Automations
  properties:
  - type: Webhooks
    url: asyncapi/leadping-webhooks.yml
  - type: Documentation
    url: https://leadping.ai/docs/validating-webhooks
- aid: leadping:leadping-analytics-api
  name: Leadping Analytics API
  description: Provides lead, communication, conversion, and organization performance analytics. Use these endpoints to measure
    activity over time, compare outcomes, and power operational dashboards and reporting workflows.
  humanURL: https://leadping.ai/docs/api-reference
  baseURL: https://api.leadping.ai
  tags:
  - Analytics
  properties:
  - type: OpenAPI
    url: openapi/leadping-analytics-api-openapi.yml
  - type: Documentation
    url: https://leadping.ai/docs
  - type: APIReference
    url: https://leadping.ai/docs/api-reference
  - type: GettingStarted
    url: https://leadping.ai/docs/sending-leads-to-leadping
  - type: Authentication
    url: authentication/leadping-authentication.yml
  - type: Conventions
    url: conventions/leadping-conventions.yml
  - type: Idempotency
    url: conventions/leadping-conventions.yml
  - type: ErrorCatalog
    url: errors/leadping-problem-types.yml
  - type: DataModel
    url: data-model/leadping-data-model.yml
  - type: RateLimits
    url: rate-limits/leadping-rate-limits.yml
  - type: Vocabulary
    url: vocabulary/leadping-vocabulary.json
- aid: leadping:leadping-automations-api
  name: Leadping Automations API
  description: 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.
  humanURL: https://leadping.ai/docs/api-reference
  baseURL: https://api.leadping.ai
  tags:
  - Automation
  tags_raw:
  - Automations
  properties:
  - type: OpenAPI
    url: openapi/leadping-automations-api-openapi.yml
  - type: Documentation
    url: https://leadping.ai/docs
  - type: APIReference
    url: https://leadping.ai/docs/api-reference
  - type: GettingStarted
    url: https://leadping.ai/docs/sending-leads-to-leadping
  - type: Authentication
    url: authentication/leadping-authentication.yml
  - type: Conventions
    url: conventions/leadping-conventions.yml
  - type: Idempotency
    url: conventions/leadping-conventions.yml
  - type: ErrorCatalog
    url: errors/leadping-problem-types.yml
  - type: DataModel
    url: data-model/leadping-data-model.yml
  - type: RateLimits
    url: rate-limits/leadping-rate-limits.yml
  - type: Vocabulary
    url: vocabulary/leadping-vocabulary.json
- aid: leadping:leadping-callevents-api
  name: Leadping Call Events API
  description: Provides call event records for auditing, diagnostics, and reporting. Use these endpoints to search and inspect
    lifecycle events emitted as Leadping calls are initiated, connected, completed, or fail.
  humanURL: https://leadping.ai/docs/api-reference
  baseURL: https://api.leadping.ai
  tags:
  - CallEvents
  tags_raw:
  - CallEvents
  properties:
  - type: OpenAPI
    url: openapi/leadping-callevents-api-openapi.yml
  - type: Documentation
    url: https://leadping.ai/docs
  - type: APIReference
    url: https://leadping.ai/docs/api-reference
  - type: GettingStarted
    url: https://leadping.ai/docs/sending-leads-to-leadping
  - type: Authentication
    url: authentication/leadping-authentication.yml
  - type: Conventions
    url: conventions/leadping-conventions.yml
  - type: Idempotency
    url: conventions/leadping-conventions.yml
  - type: ErrorCatalog
    url: errors/leadping-problem-types.yml
  - type: DataModel
    url: data-model/leadping-data-model.yml
  - type: RateLimits
    url: rate-limits/leadping-rate-limits.yml
  - type: Vocabulary
    url: vocabulary/leadping-vocabulary.json
- aid: leadping:leadping-calls-api
  name: Leadping Calls API
  description: 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.
  humanURL: https://leadping.ai/docs/api-reference
  baseURL: https://api.leadping.ai
  tags:
  - Calls
  properties:
  - type: OpenAPI
    url: openapi/leadping-calls-api-openapi.yml
  - type: Documentation
    url: https://leadping.ai/docs
  - type: APIReference
    url: https://leadping.ai/docs/api-reference
  - type: GettingStarted
    url: https://leadping.ai/docs/sending-leads-to-leadping
  - type: Authentication
    url: authentication/leadping-authentication.yml
  - type: Conventions
    url: conventions/leadping-conventions.yml
  - type: Idempotency
    url: conventions/leadping-conventions.yml
  - type: ErrorCatalog
    url: errors/leadping-problem-types.yml
  - type: DataModel
    url: data-model/leadping-data-model.yml
  - type: RateLimits
    url: rate-limits/leadping-rate-limits.yml
  - type: Vocabulary
    url: vocabulary/leadping-vocabulary.json
- aid: leadping:leadping-contact-api
  name: Leadping Contact API
  description: Accepts public contact and website inquiry submissions for Leadping. Use these endpoints to send a structured
    support or sales inquiry from an application or submit the Leadping website contact form.
  humanURL: https://leadping.ai/docs/api-reference
  baseURL: https://api.leadping.ai
  tags:
  - Contact
  properties:
  - type: OpenAPI
    url: openapi/leadping-contact-api-openapi.yml
  - type: Documentation
    url: https://leadping.ai/docs
  - type: APIReference
    url: https://leadping.ai/docs/api-reference
  - type: GettingStarted
    url: https://leadping.ai/docs/sending-leads-to-leadping
  - type: Authentication
    url: authentication/leadping-authentication.yml
  - type: Conventions
    url: conventions/leadping-conventions.yml
  - type: Idempotency
    url: conventions/leadping-conventions.yml
  - type: ErrorCatalog
    url: errors/leadping-problem-types.yml
  - type: DataModel
    url: data-model/leadping-data-model.yml
  - type: RateLimits
    url: rate-limits/leadping-rate-limits.yml
  - type: Vocabulary
    url: vocabulary/leadping-vocabulary.json
- aid: leadping:leadping-conversations-api
  name: Leadping Conversations API
  description: Provides lead conversation timelines and inbox-oriented conversation views. Use these endpoints to list recent
    conversations and retrieve the cross-channel communication history associated with a lead.
  humanURL: https://leadping.ai/docs/api-reference
  baseURL: https://api.leadping.ai
  tags:
  - Conversations
  properties:
  - type: OpenAPI
    url: openapi/leadping-conversations-api-openapi.yml
  - type: Documentation
    url: https://leadping.ai/docs
  - type: APIReference
    url: https://leadping.ai/docs/api-reference
  - type: GettingStarted
    url: https://leadping.ai/docs/sending-leads-to-leadping
  - type: Authentication
    url: authentication/leadping-authentication.yml
  - type: Conventions
    url: conventions/leadping-conventions.yml
  - type: Idempotency
    url: conventions/leadping-conventions.yml
  - type: ErrorCatalog
    url: errors/leadping-problem-types.yml
  - type: DataModel
    url: data-model/leadping-data-model.yml
  - type: RateLimits
    url: rate-limits/leadping-rate-limits.yml
  - type: Vocabulary
    url: vocabulary/leadping-vocabulary.json
- aid: leadping:leadping-events-api
  name: Leadping Events API
  description: Provides a unified record of Leadping activity across communication channels. Use these endpoints to retrieve
    event timelines, search event history, inspect event details, and record supported application events.
  humanURL: https://leadping.ai/docs/api-reference
  baseURL: https://api.leadping.ai
  tags:
  - Event
  tags_raw:
  - Events
  properties:
  - type: OpenAPI
    url: openapi/leadping-events-api-openapi.yml
  - type: Documentation
    url: https://leadping.ai/docs
  - type: APIReference
    url: https://leadping.ai/docs/api-reference
  - type: GettingStarted
    url: https://leadping.ai/docs/sending-leads-to-leadping
  - type: Authentication
    url: authentication/leadping-authentication.yml
  - type: Conventions
    url: conventions/leadping-conventions.yml
  - type: Idempotency
    url: conventions/leadping-conventions.yml
  - type: ErrorCatalog
    url: errors/leadping-problem-types.yml
  - type: DataModel
    url: data-model/leadping-data-model.yml
  - type: RateLimits
    url: rate-limits/leadping-rate-limits.yml
  - type: Vocabulary
    url: vocabulary/leadping-vocabulary.json
- aid: leadping:leadping-feedback-api
  name: Leadping Feedback API
  description: Captures Leadping product feedback and supports administrative triage. Users can submit feedback, while authorized
    staff can search, inspect, classify, and update feedback throughout the review process.
  humanURL: https://leadping.ai/docs/api-reference
  baseURL: https://api.leadping.ai
  tags:
  - Feedback
  properties:
  - type: OpenAPI
    url: openapi/leadping-feedback-api-openapi.yml
  - type: Documentation
    url: https://leadping.ai/docs
  - type: APIReference
    url: https://leadping.ai/docs/api-reference
  - type: GettingStarted
    url: https://leadping.ai/docs/sending-leads-to-leadping
  - type: Authentication
    url: authentication/leadping-authentication.yml
  - type: Conventions
    url: conventions/leadping-conventions.yml
  - type: Idempotency
    url: conventions/leadping-conventions.yml
  - type: ErrorCatalog
    url: errors/leadping-problem-types.yml
  - type: DataModel
    url: data-model/leadping-data-model.yml
  - type: RateLimits
    url: rate-limits/leadping-rate-limits.yml
  - type: Vocabulary
    url: vocabulary/leadping-vocabulary.json
- aid: leadping:leadping-leads-api
  name: Leadping Leads API
  description: 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.
  humanURL: https://leadping.ai/docs/api-reference
  baseURL: https://api.leadping.ai
  tags:
  - Leads
  properties:
  - type: OpenAPI
    url: openapi/leadping-leads-api-openapi.yml
  - type: Documentation
    url: https://leadping.ai/docs
  - type: APIReference
    url: https://leadping.ai/docs/api-reference
  - type: GettingStarted
    url: https://leadping.ai/docs/sending-leads-to-leadping
  - type: Authentication
    url: authentication/leadping-authentication.yml
  - type: Conventions
    url: conventions/leadping-conventions.yml
  - type: Idempotency
    url: conventions/leadping-conventions.yml
  - type: ErrorCatalog
    url: errors/leadping-problem-types.yml
  - type: DataModel
    url: data-model/leadping-data-model.yml
  - type: RateLimits
    url: rate-limits/leadping-rate-limits.yml
  - type: Vocabulary
    url: vocabulary/leadping-vocabulary.json
- aid: leadping:leadping-leadstatuschanges-api
  name: Leadping Lead Status Changes API
  description: Manages the auditable history of lead status transitions. Use these endpoints to change a lead's status, correct
    transition records, search status history, and export status activity for reporting.
  humanURL: https://leadping.ai/docs/api-reference
  baseURL: https://api.leadping.ai
  tags:
  - LeadStatusChanges
  properties:
  - type: OpenAPI
    url: openapi/leadping-leadstatuschanges-api-openapi.yml
  - type: Documentation
    url: https://leadping.ai/docs
  - type: APIReference
    url: https://leadping.ai/docs/api-reference
  - type: GettingStarted
    url: https://leadping.ai/docs/sending-leads-to-leadping
  - type: Authentication
    url: authentication/leadping-authentication.yml
  - type: Conventions
    url: conventions/leadping-conventions.yml
  - type: Idempotency
    url: conventions/leadping-conventions.yml
  - type: ErrorCatalog
    url: errors/leadping-problem-types.yml
  - type: DataModel
    url: data-model/leadping-data-model.yml
  - type: RateLimits
    url: rate-limits/leadping-rate-limits.yml
  - type: Vocabulary
    url: vocabulary/leadping-vocabulary.json
- aid: leadping:leadping-notifications-api
  name: Leadping Notifications API
  description: Manages user notifications, announcements, and push-notification installations. Use these endpoints to retrieve
    notification feeds and unread counts, update read state, and register or remove client push installations.
  humanURL: https://leadping.ai/docs/api-reference
  baseURL: https://api.leadping.ai
  tags:
  - Notification
  tags_raw:
  - Notifications
  properties:
  - type: OpenAPI
    url: openapi/leadping-notifications-api-openapi.yml
  - type: Documentation
    url: https://leadping.ai/docs
  - type: APIReference
    url: https://leadping.ai/docs/api-reference
  - type: GettingStarted
    url: https://leadping.ai/docs/sending-leads-to-leadping
  - type: Authentication
    url: authentication/leadping-authentication.yml
  - type: Conventions
    url: conventions/leadping-conventions.yml
  - type: Idempotency
    url: conventions/leadping-conventions.yml
  - type: ErrorCatalog
    url: errors/leadping-problem-types.yml
  - type: DataModel
    url: data-model/leadping-data-model.yml
  - type: RateLimits
    url: rate-limits/leadping-rate-limits.yml
  - type: Vocabulary
    url: vocabulary/leadping-vocabulary.json
- aid: leadping:leadping-organizations-api
  name: Leadping Organizations API
  description: Manages Leadping organizations, memberships, invitations, settings, and API credentials. Use these endpoints
    to maintain organization profiles and branding, manage members and invitations, configure options, and issue or revoke
    organization API keys.
  humanURL: https://leadping.ai/docs/api-reference
  baseURL: https://api.leadping.ai
  tags:
  - Organization
  tags_raw:
  - Organizations
  properties:
  - type: OpenAPI
    url: openapi/leadping-organizations-api-openapi.yml
  - type: Documentation
    url: https://leadping.ai/docs
  - type: APIReference
    url: https://leadping.ai/docs/api-reference
  - type: GettingStarted
    url: https://leadping.ai/docs/sending-leads-to-leadping
  - type: Authentication
    url: authentication/leadping-authentication.yml
  - type: Conventions
    url: conventions/leadping-conventions.yml
  - type: Idempotency
    url: conventions/leadping-conventions.yml
  - type: ErrorCatalog
    url: errors/leadping-problem-types.yml
  - type: DataModel
    url: data-model/leadping-data-model.yml
  - type: RateLimits
    url: rate-limits/leadping-rate-limits.yml
  - type: Vocabulary
    url: vocabulary/leadping-vocabulary.json
- aid: leadping:leadping-outbounddelivery-api
  name: Leadping Outbound Delivery API
  description: Reports outbound delivery pacing and sending capacity for the current organization. Use these endpoints to
    determine whether outbound communications can proceed and to understand active throttles, limits, or capacity constraints.
  humanURL: https://leadping.ai/docs/api-reference
  baseURL: https://api.leadping.ai
  tags:
  - OutboundDelivery
  properties:
  - type: OpenAPI
    url: openapi/leadping-outbounddelivery-api-openapi.yml
  - type: Documentation
    url: https://leadping.ai/docs
  - type: APIReference
    url: https://leadping.ai/docs/api-reference
  - type: GettingStarted
    url: https://leadping.ai/docs/sending-leads-to-leadping
  - type: Authentication
    url: authentication/leadping-authentication.yml
  - type: Conventions
    url: conventions/leadping-conventions.yml
  - type: Idempotency
    url: conventions/leadping-conventions.yml
  - type: ErrorCatalog
    url: errors/leadping-problem-types.yml
  - type: DataModel
    url: data-model/leadping-data-model.yml
  - type: RateLimits
    url: rate-limits/leadping-rate-limits.yml
  - type: Vocabulary
    url: vocabulary/leadping-vocabulary.json
- aid: leadping:leadping-sms-api
  name: Leadping Sms API
  description: Sends and manages SMS and MMS communications through Leadping. Use these endpoints to send messages, upload
    MMS media, and cancel eligible scheduled messages while preserving conversation and delivery tracking.
  humanURL: https://leadping.ai/docs/api-reference
  baseURL: https://api.leadping.ai
  tags:
  - SMS
  tags_raw:
  - Sms
  properties:
  - type: OpenAPI
    url: openapi/leadping-sms-api-openapi.yml
  - type: Documentation
    url: https://leadping.ai/docs
  - type: APIReference
    url: https://leadping.ai/docs/api-reference
  - type: GettingStarted
    url: https://leadping.ai/docs/sending-leads-to-leadping
  - type: Authentication
    url: authentication/leadping-authentication.yml
  - type: Conventions
    url: conventions/leadping-conventions.yml
  - type: Idempotency
    url: conventions/leadping-conventions.yml
  - type: ErrorCatalog
    url: errors/leadping-problem-types.yml
  - type: DataModel
    url: data-model/leadping-data-model.yml
  - type: RateLimits
    url: rate-limits/leadping-rate-limits.yml
  - type: Vocabulary
    url: vocabulary/leadping-vocabulary.json
- aid: leadping:leadping-smsevents-api
  name: Leadping Sms Events API
  description: Provides SMS and MMS event records for delivery tracking and diagnostics. Use these endpoints to search and
    inspect message lifecycle events, including outbound delivery updates and inbound messaging activity.
  humanURL: https://leadping.ai/docs/api-reference
  baseURL: https://api.leadping.ai
  tags:
  - SmsEvents
  properties:
  - type: OpenAPI
    url: openapi/leadping-smsevents-api-openapi.yml
  - type: Documentation
    url: https://leadping.ai/docs
  - type: APIReference
    url: https://leadping.ai/docs/api-reference
  - type: GettingStarted
    url: https://leadping.ai/docs/sending-leads-to-leadping
  - type: Authentication
    url: authentication/leadping-authentication.yml
  - type: Conventions
    url: conventions/leadping-conventions.yml
  - type: Idempotency
    url: conventions/leadping-conventions.yml
  - type: ErrorCatalog
    url: errors/leadping-problem-types.yml
  - type: DataModel
    url: data-model/leadping-data-model.yml
  - type: RateLimits
    url: rate-limits/leadping-rate-limits.yml
  - type: Vocabulary
    url: vocabulary/leadping-vocabulary.json
- aid: leadping:leadping-sources-api
  name: Leadping Sources API
  description: Manages lead sources, intake credentials, routing defaults, and attribution. Use these endpoints to create
    and configure sources, search source records, inspect source activity, rotate intake access, and remove obsolete sources.
  humanURL: https://leadping.ai/docs/api-reference
  baseURL: https://api.leadping.ai
  tags:
  - Sources
  properties:
  - type: OpenAPI
    url: openapi/leadping-sources-api-openapi.yml
  - type: Documentation
    url: https://leadping.ai/docs
  - type: APIReference
    url: https://leadping.ai/docs/api-reference
  - type: GettingStarted
    url: https://leadping.ai/docs/sending-leads-to-leadping
  - type: Authentication
    url: authentication/leadping-authentication.yml
  - type: Conventions
    url: conventions/leadping-conventions.yml
  - type: Idempotency
    url: conventions/leadping-conventions.yml
  - type: ErrorCatalog
    url: errors/leadping-problem-types.yml
  - type: DataModel
    url: data-model/leadping-data-model.yml
  - type: RateLimits
    url: rate-limits/leadping-rate-limits.yml
  - type: Vocabulary
    url: vocabulary/leadping-vocabulary.json
- aid: leadping:leadping-suppressions-api
  name: Leadping Suppressions API
  description: Manages recipient suppression state for compliant Leadping communication workflows. Use these endpoints to
    check contact eligibility, record or release suppressions, and review suppression history before sending messages or placing
    calls.
  humanURL: https://leadping.ai/docs/api-reference
  baseURL: https://api.leadping.ai
  tags:
  - Suppressions
  properties:
  - type: OpenAPI
    url: openapi/leadping-suppressions-api-openapi.yml
  - type: Documentation
    url: https://leadping.ai/docs
  - type: APIReference
    url: https://leadping.ai/docs/api-reference
  - type: GettingStarted
    url: https://leadping.ai/docs/sending-leads-to-leadping
  - type: Authentication
    url: authentication/leadping-authentication.yml
  - type: Conventions
    url: conventions/leadping-conventions.yml
  - type: Idempotency
    url: conventions/leadping-conventions.yml
  - type: ErrorCatalog
    url: errors/leadping-problem-types.yml
  - type: DataModel
    url: data-model/leadping-data-model.yml
  - type: RateLimits
    url: rate-limits/leadping-rate-limits.yml
  - type: Vocabulary
    url: vocabulary/leadping-vocabulary.json
- aid: leadping:leadping-tags-api
  name: Leadping Tags API
  description: Manages organization-defined tags for categorizing and routing leads. Use these endpoints to list, create,
    update, and archive reusable tags that support lead filtering, automation, assignment, and reporting.
  humanURL: https://leadping.ai/docs/api-reference
  baseURL: https://api.leadping.ai
  tags:
  - Tags
  properties:
  - type: OpenAPI
    url: openapi/leadping-tags-api-openapi.yml
  - type: Documentation
    url: https://leadping.ai/docs
  - type: APIReference
    url: https://leadping.ai/docs/api-reference
  - type: GettingStarted
    url: https://leadping.ai/docs/sending-leads-to-leadping
  - type: Authentication
    url: authentication/leadping-authentication.yml
  - type: Conventions
    url: conventions/leadping-conventions.yml
  - type: Idempotency
    url: conventions/leadping-conventions.yml
  - type: ErrorCatalog
    url: errors/leadping-problem-types.yml
  - type: DataModel
    url: data-model/leadping-data-model.yml
  - type: RateLimits
    url: rate-limits/leadping-rate-limits.yml
  - type: Vocabulary
    url: vocabulary/leadping-vocabulary.json
- aid: leadping:leadping-telephony-api
  name: Leadping Telephony API
  description: Provides shared authentication and bootstrap data for Leadping telephony clients. Use this endpoint to obtain
    the scoped credentials and configuration required to initialize supported calling experiences.
  humanURL: https://leadping.ai/docs/api-reference
  baseURL: https://api.leadping.ai
  tags:
  - Telephony
  properties:
  - type: OpenAPI
    url: openapi/leadping-telephony-api-openapi.yml
  - type: Documentation
    url: https://leadping.ai/docs
  - type: APIReference
    url: https://leadping.ai/docs/api-reference
  - type: GettingStarted
    url: https://leadping.ai/docs/sending-leads-to-leadping
  - type: Authentication
    url: authentication/leadping-authentication.yml
  - type: Conventions
    url: conventions/leadping-conventions.yml
  - type: Idempotency
    url: conventions/leadping-conventions.yml
  - type: ErrorCatalog
    url: errors/leadping-problem-types.yml
  - type: DataModel
    url: data-model/leadping-data-model.yml
  - type: RateLimits
    url: rate-limits/leadping-rate-limits.yml
  - type: Vocabulary
    url: vocabulary/leadping-vocabulary.json
- aid: leadping:leadping-transactions-api
  name: Leadping Transactions API
  description: Provides organization wallet and billing transaction records. Use these endpoints to search transaction history,
    inspect individual charges or credits, review transaction summaries, and issue administrative credits.
  humanURL: https://leadping.ai/docs/api-reference
  baseURL: https://api.leadping.ai
  tags:
  - Transaction
  tags_raw:
  - Transactions
  properties:
  - type: OpenAPI
    url: openapi/leadping-transactions-api-openapi.yml
  - type: Documentation
    url: https://leadping.ai/docs
  - type: APIReference
    url: https://leadping.ai/docs/api-reference
  - type: GettingStarted
    url: https://leadping.ai/docs/sending-leads-to-leadping
  - type: Authentication
    url: authentication/leadping-authentication.yml
  - type: Conventions
    url: conventions/leadping-conventions.yml
  - type: Idempotency
    url: conventions/leadping-conventions.yml
  - type: ErrorCatalog
    url: errors/leadping-problem-types.yml
  - type: DataModel
    url: data-model/leadping-data-model.yml
  - type: RateLimits
    url: rate-limits/leadping-rate-limits.yml
  - type: Vocabulary
    url: vocabulary/leadping-vocabulary.json
- aid: leadping:leadping-usage-api
  name: Leadping Usage API
  description: Provides billable usage records for Leadping services. Use these endpoints to review messaging and calling
    consumption, inspect usage summaries, and reconcile provider activity for an organization.
  humanURL: https://leadping.ai/docs/api-reference
  baseURL: https://api.leadping.ai
  tags:
  - Usage
  properties:
  - type: OpenAPI
    url: openapi/leadping-usage-api-openapi.yml
  - type: Documentation
    url: https://leadping.ai/docs
  - type: APIReference
    url: https://leadping.ai/docs/api-reference
  - type: GettingStarted
    url: https://leadping.ai/docs/sending-leads-to-leadping
  - type: Authentication
    url: authentication/leadping-authentication.yml
  - type: Conventions
    url: conventions/leadping-conventions.yml
  - type: Idempotency
    url: conventions/leadping-conventions.yml
  - type: ErrorCatalog
    url: errors/leadping-problem-types.yml
  - type: DataModel
    url: data-model/leadping-data-model.yml
  - type: RateLimits
    url: rate-limits/leadping-rate-limits.yml
  - type: Vocabulary
    url: vocabulary/leadping-vocabulary.json
- aid: leadping:leadping-userdataexports-api
  name: Leadping User Data Exports API
  description: Creates and delivers user-requested exports of Leadping account data. Use these endpoints to request an export,
    monitor its preparation status, and download the completed archive through a time-limited redirect.
  humanURL: https://leadping.ai/docs/api-reference
  baseURL: https://api.leadping.ai
  tags:
  - UserDataExports
  properties:
  - type: OpenAPI
    url: openapi/leadping-userdataexports-api-openapi.yml
  - type: Documentation
    url: https://leadping.ai/docs
  - type: APIReference
    url: https://leadping.ai/docs/api-reference
  - type: GettingStarted
    url: https://leadping.ai/docs/sending-leads-to-leadping
  - type: Authentication
    url: authentication/leadping-authentication.yml
  - type: Conventions
    url: conventions/leadping-conventions.yml
  - type: Idempotency
    url: conventions/leadping-conventions.yml
  - type: ErrorCatalog
    url: errors/leadping-problem-types.yml
  - type: DataModel
    url: data-model/leadping-data-model.yml
  - type: RateLimits
    url: rate-limits/leadping-rate-limits.yml
  - type: Vocabulary
    url: vocabulary/leadping-vocabulary.json
- aid: leadping:leadping-users-api
  name: Leadping Users API
  description: Manages the current Leadping user's profile, preferences, setup, and account workflows. Use these endpoints
    to retrieve and update user data, configure communication and compliance preferences, complete onboarding, manage plan-related
    actions, and request account operations.
  humanURL: https://leadping.ai/docs/api-reference
  baseURL: https://api.leadping.ai
  tags:
  - User
  tags_raw:
  - Users
  properties:
  - type: OpenAPI
    url: openapi/leadping-users-api-openapi.yml
  - type: Documentation
    url: https://leadping.ai/docs
  - type: APIReference
    url: https://leadping.ai/docs/api-reference
  - type: GettingStarted
    url: https://leadping.ai/docs/sending-leads-to-leadping
  - type: Authentication
    url: authentication/leadping-authentication.yml
  - type: Conventions
    url: conventions/leadping-conventions.yml
  - type: Idempotency
    url: conventions/leadping-conventions.yml
  - type: ErrorCatalog
    url: errors/leadping-problem-types.yml
  - type: DataModel
    url: data-model/leadping-data-model.yml
  - type: RateLimits
    url: rate-limits/leadping-rate-limits.yml
  - type: Vocabulary
    url: vocabulary/leadping-vocabulary.json
- aid: leadping:leadping-wallets-api
  name: Leadping Wallets API
  description: Manages organization wallet balances, funding, and credit activity. Use these endpoints to inspect wallet state
    and history, configure wallet behavior, add funds, and record credits or adjustments.
  humanURL: https://leadping.ai/docs/api-reference
  baseURL: https://api.leadping.ai
  tags:
  - Wallets
  properties:
  - type: OpenAPI
    url: openapi/leadping-wallets-api-openapi.yml
  - type: Documentation
    url: https://leadping.ai/docs
  - type: APIReference
    url: https://leadping.ai/docs/api-reference
  - type: GettingStarted
    url: https://leadping.ai/docs/sending-leads-to-leadping
  - type: Authentication
    url: authentication/leadping-authentication.yml
  - type: Conventions
    url: conventions/leadping-conventions.yml
  - type: Idempotency
    url: conventions/leadping-conventions.yml
  - type: ErrorCatalog
    url: errors/leadping-problem-types.yml
  - type: DataModel
    url: data-model/leadping-data-model.yml
  - type: RateLimits
    url: rate-limits/leadping-rate-limits.yml
  - type: Vocabulary
    url: vocabulary/leadping-vocabulary.json


# --- truncated at 32 KB (39 KB total) ---
# Full source: https://artifacts.apis.io/leadping/apis.yml

Leadping API — frequently asked questions

Does Leadping have an API?

Yes. APIs.io lists 31 APIs from Leadping, including Leadping MCP Servers, Leadping Webhook Events and Leadping Analytics API, and 28 more.

Is there an OpenAPI specification for the Leadping API?

Yes. APIs.io indexes 29 OpenAPI specifications for Leadping, each linked for download from this page.

How do I authenticate with the Leadping API?

Leadping documents its authentication (http/oauth2 · 2 schemes). The details are profiled on APIs.io as Leadping Authentication.

How much does the Leadping API cost?

Leadping publishes its prices; its Monthly plan is $60.00/ month as of 2026-10-28. APIs.io lists 9 pricing plans for Leadping, with each plan's price, limits and inclusions under Pricing on this page.

Does Leadping have an MCP server?

Yes. APIs.io lists 2 MCP servers for Leadping: Leadping operates TWO remote MCP servers: a public read-only documentation server at https://leadping.ai/docs/mcp (Mintlify-hosted, anonymous tools/list succeeds) and an authenticated organization-too

Is the Leadping API ready for AI agents?

Leadping has a Kin Score of 82.1 out of 100 (exemplar) and an Agent Readiness score of 71.7 (agent-ready), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider 
curl "https://apis.io/api/v1/providers/leadping"
All providers 
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose 
curl "https://apis.io/api/v1/providers/leadping/operations?limit=25"
How their score was established 
curl "https://apis.io/api/v1/providers/leadping/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.