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
1 maintainer
Release files for leadping 1.0.62
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| leadping-1.0.62.tar.gz | 186.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| leadping-1.0.62-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 832.7 kB
Release files / leadping-1.0.62.tar.gz
| Download URL | leadping-1.0.62.tar.gz |
|---|---|
| Size | 186.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
80c9f87de7a15bf7c45ab3ba29a43164043f93b1bcd67df33d483dbbfc58d978
|
|
BLAKE2b-256 checksum How to use checksums |
88d41db4d931f267eb79fd85b97044c6a18fd98c6bb6de25bf38a364bff72619
|
| Upload date | |
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 21, 2026.
Transparency logRelease files / leadping-1.0.62-py3-none-any.whl
| Download URL | leadping-1.0.62-py3-none-any.whl |
|---|---|
| Size | 646.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2c82536ba3dd826f85486f8d6062d8e63cd5d21458ed50eb96e5bfcca507e087
|
|
BLAKE2b-256 checksum How to use checksums |
6e0b7b1cddffc4fb6f3ed3caaa23ad932f5127795067fa7a35eb900487a44004
|
| Upload date | |
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 21, 2026.
Transparency log
