Leadping Python SDK

The official, type-safe Python SDK for the Leadping API. Use it to integrate lead management, conversations, SMS and calling, automations, reporting, billing, and business settings into Python applications.

The package is generated from the Leadping OpenAPI specification with Microsoft Kiota. It contains asynchronous request builders and models; your application supplies the HTTP request adapter, credentials, retry policy, and credential storage.

Installation

Install the SDK and Kiota's httpx request adapter:

python -m pip install leadping microsoft-kiota-http

Authentication

Set LEADPING_API_KEY to a WorkOS organization API key (sk_...). The SDK sends it as Authorization: Bearer <credential>. User access tokens are also supported when acting for a signed-in user; lp_src_... keys are only for lead-ingestion endpoints. See API authentication.

Create a client

Kiota's API-key authentication provider can place the complete Bearer value in the Authorization header:

import os

from kiota_abstractions.authentication.api_key_authentication_provider import (
    ApiKeyAuthenticationProvider,
    KeyLocation,
)
from kiota_http.httpx_request_adapter import HttpxRequestAdapter
from leadping import LeadpingOpenApiClient

credential = os.environ["LEADPING_API_KEY"]
auth_provider = ApiKeyAuthenticationProvider(
    KeyLocation.Header,
    f"Bearer {credential}",
    "Authorization",
    ["api.leadping.ai"],
)

adapter = HttpxRequestAdapter(auth_provider)
client = LeadpingOpenApiClient(adapter)

lead = await client.leads.by_id("lead-id").get()
print(lead.id)

The client defaults to https://api.leadping.ai.

Common operations

Request builders mirror the API path. Methods such as by_id() select a resource; terminal methods are asynchronous.

# Requires a user access token.
current_user = await client.users.me.get()

# Retrieve organization resources by ID.
source = await client.sources.by_id("source-id").get()
lead = await client.leads.by_id("lead-id").get()

Create and update operations accept generated request classes from the leadping package.

Resources

Metadata

Release files for leadping 1.0.75

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for leadping 1.0.75
File	Size	Uploaded
leadping-1.0.75.tar.gz	191.3 kB	Oct 12, 2026	Details

Built distribution (wheel)

Table of built distributions (wheels) for leadping 1.0.75
File	Interpreter	ABI	Platform	Reset
leadping-1.0.75-py3-none-any.whl 661.4 kB Oct 12, 2026	Python 3	none	any	Details

Total release size: 852.7 kB

Release files / leadping-1.0.75.tar.gz

Download URL	leadping-1.0.75.tar.gz
Size	191.3 kB
Tags	Source
SHA-256 checksum How to use checksums	`a75d6f52f0c86f19767dd87e4fd8f50366df9812593211f4e3db73ec455ec6c1`
BLAKE2b-256 checksum How to use checksums	`dea78392816523728253d063033084f5227ab0e6c77db737146d75ae67894a0a`
Upload date	Oct 12, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/leadpingai/leadping-python
Publishing commit: github.com/leadpingai/leadping-python/tree/89ee56b5161d0d9634675a6c7fecbb4230cbbf79

Workflow

Publishing configuration: github.com/leadpingai/leadping-python/blob/89ee56b5161d0d9634675a6c7fecbb4230cbbf79/.github/workflows/publish.yml
Publishing logs: github.com/leadpingai/leadping-python/actions/runs/38191749924/attempts/1

Artifact

Subject: leadping-1.0.75.tar.gz
SHA-256 checksum: a75d6f52f0c86f19767dd87e4fd8f50366df9812593211f4e3db73ec455ec6c1 Verifying attestations

Release files / leadping-1.0.75-py3-none-any.whl

Download URL	leadping-1.0.75-py3-none-any.whl
Size	661.4 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`5ae339c9b910e206a604e3cdd32c4100f42ef0662662d4d921a3c494d746e301`
BLAKE2b-256 checksum How to use checksums	`0d0364069bff518ea624750ed024cca4b63a3fa0541de5146c49eee2240fba2d`
Upload date	Oct 12, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/leadpingai/leadping-python
Publishing commit: github.com/leadpingai/leadping-python/tree/89ee56b5161d0d9634675a6c7fecbb4230cbbf79

Workflow

Publishing configuration: github.com/leadpingai/leadping-python/blob/89ee56b5161d0d9634675a6c7fecbb4230cbbf79/.github/workflows/publish.yml
Publishing logs: github.com/leadpingai/leadping-python/actions/runs/38191749924/attempts/1

Artifact

Subject: leadping-1.0.75-py3-none-any.whl
SHA-256 checksum: 5ae339c9b910e206a604e3cdd32c4100f42ef0662662d4d921a3c494d746e301 Verifying attestations