Skip to main content
There are two main ways to connect software to Leadping:
  • Send leads in from a form, partner, CRM, or posting system.
  • Work with a business account through the API or a generated SDK.
Those paths use different credentials on purpose. Choose the path before you start coding.

​
Choose what you are building

A source key can create leads only through approved ingestion routes. It cannot read account data or act as a business API key. Keeping those credentials separate limits the impact of an exposed posting credential.

​
The API workflow

1

Choose the identity

Decide whether the caller is an external lead source, a signed-in user, or a service acting for a business.
2

Use the matching credential

Follow API Authentication and keep the credential outside source code.
3

Choose raw HTTP or an SDK

Use the API Reference for endpoint-level details or a generated SDK for typed route builders and models.
4

Handle production behavior

Respect rate limits, validate responses, retry only when safe, and make operations idempotent where duplicate work would matter.

​
Security baseline

Every production integration should:
  • use HTTPS;
  • store keys and tokens in protected runtime configuration or a secret manager;
  • grant only the access the integration needs;
  • avoid logging credentials or sensitive payloads;
  • rotate exposed credentials promptly;
  • validate webhook signatures before processing side effects; and
  • treat exported lead and conversation data as sensitive.
See Security at Leadping for the platform protection model and customer responsibilities.

​
Pick a language

Leadping publishes generated SDKs for:

TypeScript

Python

.NET

Go

PHP

Java

If the SDK does not cover your runtime or you need a one-off request, use the HTTP examples in the API Reference.