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 for an organization.
Leadping Usage API is one of 29 APIs that Leadping publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Usage. 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 2 operations across 2 paths, and defines 14 schemas. It is described by OpenAPI 3.2.0, at version v1.
Requests are made against a single base URL, https://api.leadping.ai.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Leadping Usage 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 2
Across 2 paths, the API surfaces 2 operations — 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Provides billable usage records for Leadping services. Use these endpoints to review messaging and calling consumption, inspect usage summaries, and reconcile provider activity fo…
Schemas 14
The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are UsageLedgerTableRow (18 properties), UsageSummaryResponse (9 properties), RequestDataOptions (8 properties), UsageSummaryLine (6 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Leadping 12
Other APIs Leadping publishes across the network.
This is an independent, third-party profile of Leadping Usage 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.