Leadping

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 activity for reporting.

GitHub OpenAPI
Business capability
Opportunity & Pipeline Management BC-410.30

Operations 7

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

PUT /leads/{leadId}/status Set a lead's current status · Set a lead's current status #
Ask an LLM
“How do I record an outcome like appointment set on a lead?”
“Can I schedule a callback time when changing a lead's status?”
Tell an agent
Set lead {leadId}'s status to type {type} with outcome {outcome}.
Mark lead {leadId} as {outcome} ({type}) with a callback at {callbackAt}.
PUT /lead-status-changes/{id} Edit a status history entry · Update a lead status history entry #
Ask an LLM
“Can I fix a status change that was logged with the wrong outcome?”
“If I edit the latest status entry, does the lead's current status change too?”
Tell an agent
Update status history entry {id} to type {type}, outcome {outcome}.
Correct history entry {id}: outcome {outcome}, type {type}, notes {notes}.
GET /lead-status-changes/{id} Get a status history entry · Get a lead status history entry #
Ask an LLM
“How do I look at a single past status change and its notes?”
“What follow-up context was saved with a particular outcome record?”
Tell an agent
Show status change {id}.
Get the notes on lead status history entry {id}.
DELETE /lead-status-changes/{id} Delete a status history entry · Delete a lead status history entry #
Ask an LLM
“How do I remove an outcome record that shouldn't show in reports?”
“Can a mistaken status change be deleted from a lead's history?”
Tell an agent destructive · confirm first
Delete status change {id}.
Remove lead status history entry {id}.
POST /lead-status-changes/all/my List organization status history · List current-organization lead status history #
Ask an LLM
“Which status changes happened across my whole organization?”
“Can I report on lead outcomes org-wide with filters?”
Tell an agent
List all lead status changes in my organization.
Search organization status history for {search}.
GET /leads/{leadId}/status-history List a lead's status history · List a lead's status history #
Ask an LLM
“What outcomes has a single lead gone through over time?”
“Who changed a lead's status and when?”
Tell an agent
Show the status history of lead {leadId}.
List prior outcomes and notes for lead {leadId}.
GET /leads/{leadId}/status-history/export Export a lead's status history · Export a lead's status history #
Ask an LLM
“Can I export one lead's outcome history for a handoff?”
“How do I get a packaged copy of a lead's status changes for audit?”
Tell an agent
Export the status history of lead {leadId}.
Download lead {leadId}'s outcome history as an export.

Documentation

📖
Documentation
https://leadping.ai/docs
📖
APIReference
https://leadping.ai/docs/api-reference
📖
GettingStarted
https://leadping.ai/docs/sending-leads-to-leadping
📖
Authentication
https://raw.githubusercontent.com/api-evangelist/leadping/refs/heads/main/authentication/leadping-authentication.yml
📖
RateLimits
https://raw.githubusercontent.com/api-evangelist/leadping/refs/heads/main/rate-limits/leadping-rate-limits.yml

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/leadping/refs/heads/main/openapi/leadping-leadstatuschanges-api-openapi.yml

Other Resources

🔗
Conventions
https://raw.githubusercontent.com/api-evangelist/leadping/refs/heads/main/conventions/leadping-conventions.yml
🔗
Idempotency
https://raw.githubusercontent.com/api-evangelist/leadping/refs/heads/main/conventions/leadping-conventions.yml
🔗
ErrorCatalog
https://raw.githubusercontent.com/api-evangelist/leadping/refs/heads/main/errors/leadping-problem-types.yml
🔗
DataModel
https://raw.githubusercontent.com/api-evangelist/leadping/refs/heads/main/data-model/leadping-data-model.yml
🔗
Vocabulary
https://raw.githubusercontent.com/api-evangelist/leadping/refs/heads/main/vocabulary/leadping-vocabulary.json

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API 
curl "https://apis.io/api/v1/apis/leadping:leadping-leadstatuschanges-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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.

OpenAPI Specification

leadping-leadstatuschanges-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Leadping Lead Status Changes API
  description: The Leadping API helps businesses capture and manage leads, automate follow-up, send SMS and MMS messages, place calls, track conversations, enforce contact suppression, and analyze communication workflows. Use this OpenAPI 3.1 contract to integrate lead sources, build organization tools, or generate a typed API client. Authenticate protected operations with a Leadping user access token or WorkOS organization API key. Lead intake operations also accept a Leadping source key.
  termsOfService: https://leadping.ai/docs/terms-of-service
  contact:
    name: Leadping Support
    url: https://leadping.ai/contact
    email: support@leadping.ai
  license:
    name: MIT
    url: https://opensource.org/licenses/MIT
  version: v1
  summary: Lead management, messaging, calling, and automation API
servers:
- url: https://api.leadping.ai
  description: Production
tags:


# --- truncated at 32 KB (46 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/leadping/refs/heads/main/openapi/leadping-leadstatuschanges-api-openapi.yml