How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Leadping Suppressions API

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.

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

Tagged areas include Suppressions. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and rate-limit docs.

This API exposes 5 operations across 5 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version v1.

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

5 operations 5 paths 10 schemas 1 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.leadping.ai
Authentication
HTTP Bearer, HTTP Bearer
License
Terms of Service
Resource Areas
1

Authentication & Security 2

Leadping Suppressions API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT or organization API key) (Bearer). It accepts HTTP bearer tokens (Leadping source key) (SourceKey).

  • Bearer — Authorization header using the Bearer scheme. Accepted values are Leadping user JWT access tokens and WorkOS organization API keys beginning with sk.
  • SourceKey — Leadping source key for lead ingestion endpoints only using the Authorization header. Example: "Authorization: Bearer lpsrc...".

Paths & Operations 5

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

Suppressions 5

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

POST
/suppressions
Create or reactivate a recipient suppression
Suppressions_Suppress body → 201400401403429
POST
/suppressions/release
Release an active recipient suppression
Suppressions_Release body → 200400401403429
POST
/suppressions/check
Check whether a recipient is suppressed
Suppressions_Check body → 200400401403429
POST
/suppressions/all/my
List current-organization suppression entries
Suppressions_GetAllForCurrentOrganization body → 200401403429
GET
/suppressions/{id}
Get an organization suppression entry
Suppressions_Get 1 param → 200404401403429

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are SuppressionEntryResponse (12 properties), SuppressionCheckResult (10 properties), RequestDataOptions (8 properties), SuppressionEntryAudit (7 properties). Each schema is shown below with its type and property counts.

PagedResultOfSuppressionEntryResponse
object
Returns one page of query results together with page-size, optional total-count, and opaque continuation-cursor metadata.
4 properties
RequestDataOptions
object
Defines cursor pagination, sorting, search, exact-match filters, and range filters for a structured API query.
8 properties
ProblemDetails
object
Standard problem-details response containing machine-readable and human-readable information about an HTTP API error.
5 properties
SuppressionEntryAudit
object
Records one auditable change to a recipient suppression entry.
7 properties
SuppressionEntryResponse
object
Describes a recipient suppression that prevents outreach through one or more communication channels.
12 properties
OrderByOption
object
Defines one field and direction used to order an API query result set.
2 properties
SuppressionCheckResult
object
Reports whether Leadping may contact a recipient and identifies the active suppression when contact is blocked.
10 properties
ExactMatchFilter
object
Selects records whose named field equals a supplied scalar value.
2 properties
SuppressionEntryRequest
object
Defines a recipient and communication channel to suppress, release, or check before Leadping sends outreach.
6 properties 1 required
RangeFilter
object
Selects records by applying inclusive or exclusive lower and upper bounds to a named comparable field.
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

leadping-suppressions-api-openapi.yml Raw ↑

Other APIs Leadping publishes across the network.

Leadping MCP Servers
Leadping Webhook Events
Leadping Analytics API
Leadping Automations API
Leadping Call Events API
Leadping Calls API
Leadping Contact API
Leadping Conversations API
Leadping Events API
Leadping Feedback API
Leadping Leads API
Leadping Lead Status Changes API
Where this information came from

This is an independent, third-party profile of Leadping Suppressions API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.