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-transactions-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.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: Leadping Transactions 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:
- name: Transactions
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.
paths:
/transactions/{id}:
get:
tags:
- Transactions
summary: Get a current-user billing transaction
description: Returns one transaction visible to the current user, including amount, status, wallet context, and billing metadata.
operationId: Transactions_GetForCurrentUser
parameters:
- name: id
in: path
description: The ID of the transaction to retrieve.
required: true
schema:
type: string
responses:
'200':
description: Transaction was successfully retrieved.
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/TransactionResponse'
description: Describes billing transaction data returned by Leadping.
'404':
description: The specified transaction was not found.
content:
application/problem+json:
schema:
allOf:
- $ref: '#/components/schemas/ProblemDetails'
description: Standard problem-details response containing machine-readable and human-readable information about an HTTP API error.
example:
type: about:blank
title: Not Found
status: 404
detail: The request could not be completed.
'401':
description: The user does not own this transaction.
content:
application/problem+json:
schema:
allOf:
- $ref: '#/components/schemas/ProblemDetails'
description: Standard problem-details response containing machine-readable and human-readable information about an HTTP API error.
example:
type: about:blank
title: Unauthorized
status: 401
detail: The request could not be completed.
'403':
description: The authenticated user or organization does not have permission to perform this operation.
content:
application/problem+json:
schema:
allOf:
- $ref: '#/components/schemas/ProblemDetails'
description: Standard problem-details response containing machine-readable and human-readable information about an HTTP API error.
example:
type: about:blank
title: Forbidden
status: 403
detail: The request could not be completed.
'429':
description: The API rate limit for this account or client has been exceeded.
headers:
Retry-After:
description: Number of seconds to wait before retrying the request.
schema:
minimum: 0
type: integer
format: int32
content:
application/problem+json:
schema:
allOf:
- $ref: '#/components/schemas/ProblemDetails'
description: Standard problem-details response containing machine-readable and human-readable information about an HTTP API error.
example:
type: about:blank
title: Too Many Requests
status: 429
detail: The request could not be completed.
security:
- Bearer: []
x-agentic-access:
action-class: connected
consequences:
- read
subject:
required: true
authorization:
source: OpenAPI security requirements
audience: https://api.leadping.ai
audit:
recommended: false
/transactions/all/my:
post:
tags:
- Transactions
summary: List current-user billing transactions
description: Lists current-user transactions with paging, sorting, and filters for wallet events, billing history, and reconciliation.
operationId: Transactions_GetAllForCurrentUser
parameters:
- name: startAt
in: query
description: Optional inclusive start timestamp for transaction creation.
schema:
type: string
format: date-time
- name: endAt
in: query
description: Optional exclusive end timestamp for transaction creation.
schema:
type: string
format: date-time
requestBody:
description: Pagination, filtering, and sorting options.
content:
application/json:
schema:
$ref: '#/components/schemas/RequestDataOptions'
application/*+json:
schema:
$ref: '#/components/schemas/RequestDataOptions'
required: true
responses:
'200':
description: Transactions were successfully retrieved.
content:
application/json:
schema:
$ref: '#/components/schemas/PagedResultOfTransactionTableRow'
'401':
description: Authentication credentials are missing or invalid.
content:
application/problem+json:
schema:
allOf:
- $ref: '#/components/schemas/ProblemDetails'
description: Standard problem-details response containing machine-readable and human-readable information about an HTTP API error.
example:
type: about:blank
title: Unauthorized
status: 401
detail: The request could not be completed.
'400':
description: The request was invalid or malformed.
content:
application/problem+json:
schema:
allOf:
- $ref: '#/components/schemas/ProblemDetails'
description: Standard problem-details response containing machine-readable and human-readable information about an HTTP API error.
example:
type: about:blank
title: Bad Request
status: 400
detail: The request could not be completed.
'403':
description: The authenticated user or organization does not have permission to perform this operation.
content:
application/problem+json:
schema:
allOf:
- $ref: '#/components/schemas/ProblemDetails'
description: Standard problem-details response containing machine-readable and human-readable information about an HTTP API error.
example:
type: about:blank
title: Forbidden
status: 403
detail: The request could not be completed.
'429':
description: The API rate limit for this account or client has been exceeded.
headers:
Retry-After:
description: Number of seconds to wait before retrying the request.
schema:
minimum: 0
type: integer
format: int32
content:
application/problem+json:
schema:
allOf:
- $ref: '#/components/schemas/ProblemDetails'
description: Standard problem-details response containing machine-readable and human-readable information about an HTTP API error.
example:
type: about:blank
title: Too Many Requests
status: 429
detail: The request could not be completed.
security:
- Bearer: []
x-agentic-access:
action-class: acting
consequences:
- write
subject:
required: true
authorization:
source: OpenAPI security requirements
audience: https://api.leadping.ai
audit:
recommended: true
components:
schemas:
OrderByOption:
required:
- field
type: object
properties:
field:
type: string
direction:
enum:
- asc
- desc
type:
- 'null'
- string
TransactionType:
enum:
- Debit
- Adjustment
- Deposit
type: string
description: Classifies a wallet transaction as a debit, credit, refund, adjustment, deposit, or other balance movement.
ProblemDetails:
type: object
properties:
type:
type:
- 'null'
- string
description: URI reference that identifies the problem type.
title:
type:
- 'null'
- string
description: Short, human-readable summary of the problem.
status:
type:
- 'null'
- integer
description: HTTP status code returned for the problem.
format: int32
detail:
type:
- 'null'
- string
description: Human-readable explanation specific to this occurrence of the problem.
instance:
type:
- 'null'
- string
description: URI reference that identifies this specific occurrence of the problem.
errors:
type: object
additionalProperties:
type: array
items:
type: string
description: Validation errors keyed by the JSON request field name. Present for request validation failures.
traceId:
type: string
description: Request trace identifier used to correlate this problem with Leadping diagnostics.
description: Standard problem-details response containing machine-readable and human-readable information about an HTTP API error.
ExactMatchFilter:
required:
- field
type: object
properties:
value: {}
field:
type: string
TransactionResponse:
type: object
properties:
organization:
type:
- 'null'
- object
allOf:
- $ref: '#/components/schemas/IdNamePair'
description: Identifier and display name of the related organization.
lead:
type:
- 'null'
- object
allOf:
- $ref: '#/components/schemas/IdNamePair'
description: Identifier and display name of the related lead.
amount:
type: number
description: Monetary amount for this billing transaction or wallet operation.
format: double
netAmount:
type: number
description: Net monetary amount after fees, credits, or adjustments.
format: double
billedAmount:
type: number
description: Customer-facing amount billed for the transaction.
format: double
billingChannel:
enum:
- lead
- sms
- mms
- email
- voice
- phone_number
- warmup
- website
- openai
- domain
- 10dlc
- payment
- connection
- automation
type:
- 'null'
- string
description: Identifies the messaging, calling, phone-number, lookup, or platform channel that generated billable usage.
billableUnit:
enum:
- lead_received
- phone_identity_lookup
- sms_segment
- mms_message
- email_message
- voice_minute
- phone_number_month
- warmup_sms_segment
- warmup_voice_minute
- website_setup
- openai_operation
- domain_registration
- 10dlc_application
- 10dlc_campaign_month
- payment_processing_fee
- connection_action
- automation_run
type:
- 'null'
- string
description: Identifies the metered unit used to price Leadping usage, such as a message, call minute, lookup, or phone number.
gatewayFeeAmount:
type:
- 'null'
- number
description: Payment gateway fee amount charged for the wallet transaction.
format: double
gatewayStatus:
type:
- 'null'
- string
description: Payment gateway status returned for this transaction.
platformFeeAmount:
type:
- 'null'
- number
description: Leadping platform fee amount included in the transaction.
format: double
notes:
type:
- 'null'
- string
description: Additional billing notes that explain the transaction for admins or customers.
description:
type:
- 'null'
- string
description: Human-readable description that explains this billing transaction response to API users.
paymentMethodDisplay:
type:
- 'null'
- string
description: Masked or human-readable payment method shown for this transaction.
transactionType:
allOf:
- $ref: '#/components/schemas/TransactionType'
description: Debit or credit classification for this wallet transaction.
transactionStatus:
allOf:
- $ref: '#/components/schemas/TransactionStatus'
description: Processing status for this wallet transaction.
id:
type: string
createdAt:
type: string
format: date-time
modifiedAt:
type:
- 'null'
- string
format: date-time
description: Describes billing transaction data returned by Leadping.
RangeFilter:
required:
- field
type: object
properties:
greaterThan: {}
greaterThanOrEqual: {}
lessThan: {}
lessThanOrEqual: {}
field:
type: string
IdNamePair:
required:
- id
- name
type: object
properties:
id:
type: string
name:
type: string
description: User summary connected to this automation configuration response.
TransactionStatus:
enum:
- Pending
- Confirmed
- Failed
type: string
description: Describes the processing and settlement lifecycle of a Leadping wallet or billing transaction.
TransactionTableRow:
type: object
properties:
id:
type: string
description: Unique Leadping identifier for this billing transaction table row.
organization:
type:
- 'null'
- object
allOf:
- $ref: '#/components/schemas/IdNamePair'
description: Identifier and display name of the related organization.
lead:
type:
- 'null'
- object
allOf:
- $ref: '#/components/schemas/IdNamePair'
description: Identifier and display name of the related lead.
amount:
type: number
description: Monetary amount for this billing transaction or wallet operation.
format: double
netAmount:
type: number
description: Net monetary amount after fees, credits, or adjustments.
format: double
billedAmount:
type: number
description: Customer-facing amount billed for the metered usage or wallet transaction.
format: double
quantity:
type:
- 'null'
- number
description: Number of billable units measured for this transaction, when usage-based pricing applies.
format: double
unitPrice:
type:
- 'null'
- number
description: Price charged per billable unit when usage-based pricing applies.
format: double
billingChannel:
enum:
- lead
- sms
- mms
- email
- voice
- phone_number
- warmup
- website
- openai
- domain
- 10dlc
- payment
- connection
- automation
type:
- 'null'
- string
description: Identifies the messaging, calling, phone-number, lookup, or platform channel that generated billable usage.
billableUnit:
enum:
- lead_received
- phone_identity_lookup
- sms_segment
- mms_message
- email_message
- voice_minute
- phone_number_month
- warmup_sms_segment
- warmup_voice_minute
- website_setup
- openai_operation
- domain_registration
- 10dlc_application
- 10dlc_campaign_month
- payment_processing_fee
- connection_action
- automation_run
type:
- 'null'
- string
description: Identifies the metered unit used to price Leadping usage, such as a message, call minute, lookup, or phone number.
sourceEventId:
type:
- 'null'
- string
description: Identifier of the event that created this billing transaction, when available.
sourceEventType:
type:
- 'null'
- string
description: Event type that created this billing transaction, when available.
pricingVersion:
type:
- 'null'
- string
description: Version of the pricing rules used to calculate the billed amount.
transactionType:
allOf:
- $ref: '#/components/schemas/TransactionType'
description: Debit or credit classification for this wallet transaction.
transactionStatus:
allOf:
- $ref: '#/components/schemas/TransactionStatus'
description: Processing status for this wallet transaction.
paymentMethodDisplay:
type:
- 'null'
- string
description: Masked or human-readable payment method shown for this transaction.
description:
type:
- 'null'
- string
description: Human-readable description that explains this billing transaction table row to API users.
createdAt:
type: string
description: UTC timestamp when this billing transaction table row was created.
format: date-time
description: Summarizes billing transaction data in paginated and searchable results.
RequestDataOptions:
type: object
properties:
pageSize:
type: integer
format: int32
continuationToken:
type:
- 'null'
- string
orderBy:
type:
- 'null'
- array
items:
$ref: '#/components/schemas/OrderByOption'
includeCount:
type:
- 'null'
- boolean
search:
type:
- 'null'
- string
searchFields:
type:
- 'null'
- array
items:
type: string
filters:
type:
- 'null'
- array
items:
$ref: '#/components/schemas/ExactMatchFilter'
rangeFilters:
type:
- 'null'
- array
items:
$ref: '#/components/schemas/RangeFilter'
PagedResultOfTransactionTableRow:
type: object
properties:
items:
type: array
items:
allOf:
- $ref: '#/components/schemas/TransactionTableRow'
description: Summarizes billing transaction data in paginated and searchable results.
pageSize:
type: integer
format: int32
totalCount:
type:
- 'null'
- integer
format: int32
continuationToken:
type:
- 'null'
- string
securitySchemes:
Bearer:
type: http
description: Authorization header using the Bearer scheme. Accepted values are Leadping user JWT access tokens and WorkOS organization API keys beginning with sk_.
scheme: bearer
bearerFormat: JWT or organization API key
SourceKey:
type: http
description: 'Leadping source key for lead ingestion endpoints only using the Authorization header. Example: "Authorization: Bearer lp_src_...".'
scheme: bearer
bearerFormat: Leadping source key
externalDocs:
description: Leadping API documentation, authentication guide, concepts, and integration guidance.
url: https://leadping.ai/docs/api-reference