Skip to main content

Leadping 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.117

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.117
File Size Uploaded Provenance Actions
leadping-1.0.117.tar.gz 219.4 kB With provenance Details for leadping-1.0.117.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for leadping 1.0.117
File Interpreter ABI Platform Actions
leadping-1.0.117-py3-none-any.whl Python 3 none any Details for leadping-1.0.117-py3-none-any.whl

Total release size: 976.0 kB

Release files / leadping-1.0.117.tar.gz

Download URL leadping-1.0.117.tar.gz
Size 219.4 kB
Tags Source
SHA-256 checksum
How to use checksums
d81212811860d7d634fa18e96fbeec6599e63eb7a9695a9b4138557ea46e803b
BLAKE2b-256 checksum
How to use checksums
dd78c3851e66c6da8642cf9e726122d45cc8f5beffb909fd924821707ac85339
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 19, 2026.

Transparency log

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

Download URL leadping-1.0.117-py3-none-any.whl
Size 756.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4fdb212dfc36bc6baea98d9b5ab090b55ce71e03ca1a0f264af8b78a47cf743c
BLAKE2b-256 checksum
How to use checksums
5cd4bcc18a856813130a2dcd7f6a16b9e8791f98c6a350c8843d04f68bb20dc0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 19, 2026.

Transparency log

Security for leadping 1.0.117

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.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for leadping-1.0.117.tar.gz

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 Nov 19, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

1.0.117 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page