> ## 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 correct Leadping credential, endpoint, SDK, webhook flow, or MCP server for your integration.

Start by identifying who or what is making the request. Lead intake, user actions, organization services, webhooks, and AI tools use different trust boundaries.

## Choose the integration path

| Goal                                      | Guide                                     | Credential                     |
| ----------------------------------------- | ----------------------------------------- | ------------------------------ |
| Submit leads from a form, partner, or CRM | [Send Leads](/docs/sending-leads-to-leadping)  | Source key: `lp_src_...`       |
| Build a service for one organization      | [API Authentication](/docs/api-authentication) | Organization API key: `sk_...` |
| Call the API as a signed-in user          | [API Authentication](/docs/api-authentication) | User access token              |
| Use typed models and route builders       | [SDKs](/docs/sdks/overview)                    | Organization key or user token |
| Receive automation webhooks               | [Validate Webhooks](/docs/validating-webhooks) | Webhook signing secret         |
| Connect an AI assistant                   | [MCP Servers](/docs/mcp-server)                | Depends on the selected server |

<Warning>
  A source key authorizes the external lead-ingestion routes only. It cannot read organization data or replace a user token or organization API key.
</Warning>

## Build the integration

1. **Select the identity.** Decide whether the caller is a source, user, organization service, or webhook recipient.
2. **Use the matching credential.** Never broaden access to avoid implementing the correct authentication flow.
3. **Choose HTTP or an SDK.** Use direct HTTP for simple integrations or a generated SDK for typed models and route builders.
4. **Handle failure explicitly.** Validate status codes, respect rate limits, and retry only when the operation is safe.
5. **Test the real path.** Exercise production authentication, payload construction, error handling, and downstream effects with controlled data.

## Production baseline

* Use HTTPS for every request.
* Store credentials in protected runtime configuration or a secret manager.
* Keep credentials and sensitive payloads out of logs and URLs.
* Grant only the access the integration needs.
* Rotate exposed or unused credentials.
* Validate webhook signatures before processing side effects.
* Make retryable operations idempotent where duplicates matter.
* Treat lead, contact, and conversation data as sensitive.

## SDKs

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

Use the [API Reference](/docs/api-reference) for endpoint contracts and the [OpenAPI specification](/docs/openapi.json) for code generation or schema tooling.