Skip to main content
Leadping publishes generated SDKs for teams that want typed API clients instead of hand-built HTTP calls. The SDKs are generated from the Leadping OpenAPI document with Microsoft Kiota and use the same API surface as the API Reference. Use an SDK when your application needs authenticated Leadping API access for records, users, sources, conversations, analytics, phone numbers, SMS, calls, or other account workflows. For external systems that only need to submit new leads from an approved source, the simpler path is usually direct source-key intake through POST /leads or POST /leads/intake.

​
Choose the right integration path

​
Packages

​
Authentication

Each SDK accepts a Kiota request adapter. Most SDK integrations should attach a Leadping business API key. See API Authentication for the full credential guidance. The generated clients set https://api.leadping.ai as the base URL when the adapter does not already have one. The SDKs do not own token storage, API key storage, refresh flows, or secret rotation. Keep credentials in your application infrastructure and inject them into the Kiota request adapter. Use lp_src_... only when intentionally calling lead ingestion endpoints; it is not the normal SDK credential.

​
Client entry points

Use the SDK for typed route builders and model types. Use the API Reference when you need endpoint-specific request and response details.

​
Versioning

SDK releases use normal vX.Y.Z tags. Publish workflows automatically choose the next patch version from the latest Git tag and the relevant package registry version.

​
Language guides