> ## Documentation Index
> Fetch the complete documentation index at: https://leadping.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Build with Leadping

> Choose the right Leadping API, credential, SDK, webhook, or documentation integration for what you are building.

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

| Goal                                      | Start with                                              | Credential                     |
| ----------------------------------------- | ------------------------------------------------------- | ------------------------------ |
| Post leads from an external source        | [Sending Leads to Leadping](/docs/sending-leads-to-leadping) | Source key: `lp_src_...`       |
| Build a service or agent for a business   | [API Authentication](/docs/api-authentication)               | Business API key: `lp_...`     |
| Call the API as a signed-in user          | [API Authentication](/docs/api-authentication)               | User access token              |
| Use generated route builders and models   | [SDKs](/docs/sdks/overview)                                  | Business API key or user token |
| Receive automation webhooks               | [Validating Webhooks](/docs/validating-webhooks)             | Webhook signing secret         |
| Give an AI assistant access to these docs | [MCP Server](/docs/mcp-server)                               | No Leadping account credential |

<Warning>
  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.
</Warning>

## The API workflow

<Steps>
  <Step title="Choose the identity">
    Decide whether the caller is an external lead source, a signed-in user, or a service acting for a business.
  </Step>

  <Step title="Use the matching credential">
    Follow [API Authentication](/docs/api-authentication) and keep the credential outside source code.
  </Step>

  <Step title="Choose raw HTTP or an SDK">
    Use the [API Reference](/docs/api-reference) for endpoint-level details or a generated [SDK](/docs/sdks/overview) for typed route builders and models.
  </Step>

  <Step title="Handle production behavior">
    Respect [rate limits](/docs/rate-limits), validate responses, retry only when safe, and make operations idempotent where duplicate work would matter.
  </Step>
</Steps>

## 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](/docs/trust/security) for the platform protection model and customer responsibilities.

## Pick a language

Leadping publishes generated SDKs for:

<CardGroup cols={3}>
  <Card title="TypeScript" icon="js" href="/docs/sdks/typescript" />

  <Card title="Python" icon="python" href="/docs/sdks/python" />

  <Card title=".NET" icon="microsoft" href="/docs/sdks/dotnet" />

  <Card title="Go" icon="golang" href="/docs/sdks/go" />

  <Card title="PHP" icon="php" href="/docs/sdks/php" />

  <Card title="Java" icon="java" href="/docs/sdks/java" />
</CardGroup>

If the SDK does not cover your runtime or you need a one-off request, use the HTTP examples in the [API Reference](/docs/api-reference).