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-suppressions-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 Suppressions 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: Suppressions
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.
paths:
/suppressions:
post:
tags:
- Suppressions
summary: Create or reactivate a recipient suppression
description: The result reflects the effective compliance state after normalization, organization scoping, and suppression-history checks.
operationId: Suppressions_Suppress
requestBody:
description: The suppression entry request payload for the operation.
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/SuppressionEntryRequest'
description: Defines a recipient and communication channel to suppress, release, or check before Leadping sends outreach.
application/*+json:
schema:
allOf:
- $ref: '#/components/schemas/SuppressionEntryRequest'
description: Defines a recipient and communication channel to suppress, release, or check before Leadping sends outreach.
required: true
responses:
'201':
description: The suppression entry response was created successfully.
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/SuppressionEntryResponse'
description: Describes a recipient suppression that prevents outreach through one or more communication channels.
'400':
description: The request was invalid or failed validation.
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.
'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.
'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
/suppressions/release:
post:
tags:
- Suppressions
summary: Release an active recipient suppression
description: The result reflects the effective compliance state after normalization, organization scoping, and suppression-history checks.
operationId: Suppressions_Release
requestBody:
description: The suppression entry request payload for the operation.
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/SuppressionEntryRequest'
description: Defines a recipient and communication channel to suppress, release, or check before Leadping sends outreach.
application/*+json:
schema:
allOf:
- $ref: '#/components/schemas/SuppressionEntryRequest'
description: Defines a recipient and communication channel to suppress, release, or check before Leadping sends outreach.
required: true
responses:
'200':
description: Returns the suppression entry response.
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/SuppressionEntryResponse'
description: Describes a recipient suppression that prevents outreach through one or more communication channels.
'400':
description: The request was invalid or failed validation.
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.
'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.
'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
/suppressions/check:
post:
tags:
- Suppressions
summary: Check whether a recipient is suppressed
description: The result reflects the effective compliance state after normalization, organization scoping, and suppression-history checks.
operationId: Suppressions_Check
requestBody:
description: The suppression entry request payload for the operation.
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/SuppressionEntryRequest'
description: Defines a recipient and communication channel to suppress, release, or check before Leadping sends outreach.
application/*+json:
schema:
allOf:
- $ref: '#/components/schemas/SuppressionEntryRequest'
description: Defines a recipient and communication channel to suppress, release, or check before Leadping sends outreach.
required: true
responses:
'200':
description: Returns the suppression check result.
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/SuppressionCheckResult'
description: Reports whether Leadping may contact a recipient and identifies the active suppression when contact is blocked.
'400':
description: The request was invalid or failed validation.
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.
'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.
'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
/suppressions/all/my:
post:
tags:
- Suppressions
summary: List current-organization suppression entries
description: Returns a filtered, paginated list of recipients the current organization has blocked from phone, SMS, or email outreach.
operationId: Suppressions_GetAllForCurrentOrganization
requestBody:
description: Pagination, filtering, and sorting options for suppression entries.
content:
application/json:
schema:
$ref: '#/components/schemas/RequestDataOptions'
application/*+json:
schema:
$ref: '#/components/schemas/RequestDataOptions'
required: true
responses:
'200':
description: OK
content:
application/json:
schema:
$ref: '#/components/schemas/PagedResultOfSuppressionEntryResponse'
'400':
description: The request was invalid or failed validation.
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.
'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.
'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
/suppressions/{id}:
get:
tags:
- Suppressions
summary: Get an organization suppression entry
description: Returns one suppression entry for the current organization, including its recipient, channel, reason, status, and audit timestamps.
operationId: Suppressions_Get
parameters:
- name: id
in: path
description: The unique identifier of the suppression entry to retrieve.
required: true
schema:
type: string
responses:
'200':
description: OK
content:
application/json:
schema:
allOf:
- $ref: '#/components/schemas/SuppressionEntryResponse'
description: Describes a recipient suppression that prevents outreach through one or more communication channels.
'404':
description: The requested resource 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: 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.
'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
components:
schemas:
SuppressionEntryAudit:
type: object
properties:
id:
type: string
description: Unique identifier for this suppression audit record.
status:
type: string
description: Suppression status established by this change, such as active or released.
source:
type: string
description: System or workflow that initiated the change.
timestamp:
type: string
description: UTC timestamp when the suppression change occurred.
format: date-time
actorId:
type:
- 'null'
- string
description: Identifier of the user or system actor responsible for the change.
reason:
type:
- 'null'
- string
description: Human-readable reason recorded for the suppression change.
safeMetadata:
type: object
additionalProperties:
type: string
description: Non-sensitive metadata that provides additional audit context.
description: Records one auditable change to a recipient suppression entry.
OrderByOption:
required:
- field
type: object
properties:
field:
type: string
direction:
enum:
- asc
- desc
type:
- 'null'
- string
SuppressionCheckResult:
type: object
properties:
allowed:
type: boolean
description: Whether outreach to the recipient is allowed for the requested channel.
organizationId:
type:
- 'null'
- string
description: Identifier of the organization whose suppression list was checked.
recipientIdentifier:
type:
- 'null'
- string
description: Provider or customer identifier used to match the recipient.
normalizedPhoneNumber:
type:
- 'null'
- string
description: Phone number used for matching, normalized to a consistent format.
normalizedEmail:
type:
- 'null'
- string
description: Email address used for matching, normalized for comparison.
format: email
channel:
type:
- 'null'
- string
description: Communication channel evaluated by the suppression check.
suppressionEntryId:
type:
- 'null'
- string
description: Identifier of the active suppression that blocked contact, when one matched.
source:
type:
- 'null'
- string
description: The source value on the active suppression entry that blocked this check.
suppressedAt:
type:
- 'null'
- string
description: The date and time the blocking suppression became active.
format: date-time
customerReason:
type:
- 'null'
- string
description: Customer-safe explanation of why contact is blocked or allowed.
description: Reports whether Leadping may contact a recipient and identifies the active suppression when contact is blocked.
SuppressionEntryRequest:
type: object
properties:
recipientIdentifier:
type:
- 'null'
- string
description: Optional provider or customer identifier that uniquely identifies the recipient.
phoneNumber:
type:
- 'null'
- string
description: Recipient phone number to suppress or check, preferably in E.164 format.
email:
type:
- 'null'
- string
description: Recipient email address to suppress or check.
format: email
channel:
type: string
description: Communication channel affected by the suppression, such as SMS, voice, email, or all channels.
reason:
type:
- 'null'
- string
description: Human-readable reason for creating or releasing the suppression.
description: Defines a recipient and communication channel to suppress, release, or check before Leadping sends outreach.
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
SuppressionEntryResponse:
type: object
properties:
id:
type:
- 'null'
- string
description: Unique Leadping identifier for the suppression entry.
organizationId:
type:
- 'null'
- string
description: Identifier of the organization that owns the suppression entry.
recipientIdentifier:
type:
- 'null'
- string
description: Provider or customer identifier used to recognize the suppressed recipient.
normalizedPhoneNumber:
type:
- 'null'
- string
description: Suppressed phone number normalized to a consistent format.
normalizedEmail:
type:
- 'null'
- string
description: Suppressed email address normalized for matching.
format: email
channel:
type:
- 'null'
- string
description: Communication channel affected by the suppression, such as SMS, voice, email, or all channels.
source:
type:
- 'null'
- string
description: System or workflow that created the suppression.
status:
type:
- 'null'
- string
description: Current lifecycle state, such as active or released.
reason:
type:
- 'null'
- string
description: Human-readable reason the recipient was suppressed or subsequently released.
suppressedAt:
type:
- 'null'
- string
description: UTC timestamp when the suppression became active.
format: date-time
releasedAt:
type:
- 'null'
- string
description: UTC timestamp when the suppression was released, or null while it remains active.
format: date-time
audit:
type: array
items:
allOf:
- $ref: '#/components/schemas/SuppressionEntryAudit'
description: Records one auditable change to a recipient suppression entry.
description: Chronological audit history of suppression and release changes.
description: Describes a recipient suppression that prevents outreach through one or more communication channels.
PagedResultOfSuppressionEntryResponse:
type: object
properties:
items:
type: array
items:
allOf:
- $ref: '#/components/schemas/SuppressionEntryResponse'
description: Describes a recipient suppression that prevents outreach through one or more communication channels.
pageSize:
type: integer
format: int32
totalCount:
type:
- 'null'
- integer
format: int32
continuationToken:
type:
- 'null'
- string
RangeFilter:
required:
- field
type: object
properties:
greaterThan: {}
greaterThanOrEqual: {}
lessThan: {}
lessThanOrEqual: {}
field:
type: string
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'
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