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.116

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.116
File Size Uploaded Provenance Actions
leadping-1.0.116.tar.gz 218.9 kB With provenance Details for leadping-1.0.116.tar.gz

Built distribution (wheel)

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

Total release size: 973.7 kB

Release files / leadping-1.0.116.tar.gz

Download URL leadping-1.0.116.tar.gz
Size 218.9 kB
Tags Source
SHA-256 checksum
How to use checksums
5b9bf6d12fe2eda6bef7c7e4149c33a2a43bc936510b690ff3afa55a0ae8922d
BLAKE2b-256 checksum
How to use checksums
987d820f69ef5872e1b9b52ae7636bd7ebac433e91bb7df82d85bf42062c0ed0
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.116-py3-none-any.whl

Download URL leadping-1.0.116-py3-none-any.whl
Size 754.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e4282156424b3eacdd1b55cae9cc8cd8f1a45a35bd4c4ea78f9212b46d3cc5c7
BLAKE2b-256 checksum
How to use checksums
ed370e8a3071cdc98eedbd061833c1033ad0f9fff5d3a5e51860d135abded6ef
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.116

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.116.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.116 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