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 Users API

Manages the current Leadping user's profile, preferences, setup, and account workflows. Use these endpoints to retrieve and update user data, configure communication and compliance preferences, complete onboarding, manage plan-related actions, and request account operations.

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

Tagged areas include User. 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 4 paths, and defines 15 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 4 paths 15 schemas 2 GET3 PUT

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 Users 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 4 paths, the API surfaces 5 operations — 2 GET, 3 PUT. Each is listed below with its method, path, parameters, and response codes.

Users 5

Manages the current Leadping user's profile, preferences, setup, and account workflows. Use these endpoints to retrieve and update user data, configure communication and complianc…

GET
/users/me/paymentmethod
Get current user's billing payment method
Users_GetPaymentMethodForCurrentUser → 200400401429
GET
/users/me
Get current user account profile details
Users_GetForCurrentUser → 200404401429
PUT
/users/me
Update current user account profile
Users_UpdateForCurrentUser body → 200400401429
PUT
/users/change-billing-plan
Change the current user's billing plan
Users_ChangeBillingPlan body → 200400404401429
PUT
/users/compliance
Update current user compliance settings
Users_UpdateCompliance body → 200400401429

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are UserNotificationPreferences (27 properties), UserResponse (23 properties), OrganizationBillingState (13 properties), UserRequest (12 properties). Each schema is shown below with its type and property counts.

TrustedFormCertificate
object
Describes trusted form certificate data used in Leadping API requests and responses.
4 properties
OrganizationBillingState
object
Customer-safe billing state for a Leadping organization.
13 properties
StripePaymentMethodResponse
object
Describes stripe payment method data used in Leadping API requests and responses.
7 properties 3 required
UserResponse
object
Describes user data returned by Leadping.
23 properties
UserNotificationPreferences
object
Describes user notification preferences data used in Leadping API requests and responses.
27 properties
BillingPlan
string
Identifies the Leadping subscription plan that determines organization features, allowances, and billing behavior.
IdNamePair
object
Provides a compact API reference to another resource using its stable identifier and human-readable display name.
2 properties 2 required
ChangeBillingPlanRequest
object
Defines the input used for change billing plan.
2 properties 1 required
MobileDevicePreferences
object
Describes notification and calling preferences saved for one of the user's mobile devices.
3 properties
UserIdentity
object
Identifies an external sign-in identity linked to a Leadping user, including its provider, provider-assigned user identifier, and authentication method.
3 properties
UserCompliance
object
Describes user compliance data used in Leadping API requests and responses.
6 properties
ProblemDetails
object
Standard problem-details response containing machine-readable and human-readable information about an HTTP API error.
5 properties
UserRequest
object
Defines the fields clients can send when working with user profile.
12 properties 2 required
OrganizationDunningInfo
object
Dunning state recorded after a failed recurring payment.
10 properties
ComplianceUpdateRequest
object
Defines the input used for compliance update.
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

leadping-users-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 Users 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.