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

# Configure Lead Sources

> Create a Leadping source, use its source key, monitor lead volume, and manage its intake access.

A source identifies the form, website, partner, CRM, or other intake path sending leads to Leadping. Each source has its own key so Leadping can authenticate and attribute incoming leads.

Create separate sources when you need to identify or disable intake paths independently.

<Warning>
  Every external lead must include its own TrustedForm certificate URL. Creating or enabling a source does not remove that requirement.
</Warning>

## Create a source

1. Open **Sources** in Leadping.
2. Select **Add source**.
3. Enter a name that identifies the real intake path.
4. Select **Create source**.
5. Copy the generated source API key into the posting system.

Use a name that remains clear to another operator, such as `Acme Solar — Website Quote Form` or `Northstar CRM Import`.

A new source is enabled immediately and shows **Not yet used** until it receives its first lead.

## Source status

| Status                    | Meaning                                           |
| ------------------------- | ------------------------------------------------- |
| Not yet used              | The source is enabled but has not received a lead |
| Receiving leads or Active | The enabled source has received at least one lead |
| Disabled                  | Its source key cannot submit leads                |

## Use the source key

Send the key as a Bearer token to either supported external intake endpoint:

```http theme={null}
POST https://api.leadping.ai/leads/intake
Authorization: Bearer lp_src_example
Content-Type: application/json
```

Source keys work with:

* `POST /leads`
* `POST /leads/intake`

They do not provide access to organization data or other API operations.

Protect the key as a secret:

* store it outside source code;
* send it only over HTTPS;
* keep it out of payloads, URLs, and logs; and
* rotate it if exposed.

## Review a source

The source page provides:

| Area           | Available information                          |
| -------------- | ---------------------------------------------- |
| Status         | Whether the source can currently receive leads |
| Source API key | The credential used by the posting system      |
| Metrics        | Lead volume over the selected date range       |
| Configuration  | The source name                                |
| Logs           | Recorded source activity                       |

The source list also shows when the source last received a lead and when its configuration was last updated.

## Test the intake path

1. Submit a lead from the real form, partner, CRM, or posting system.
2. Confirm the source changes from **Not yet used** to an active state.
3. Open the lead and verify its source, TrustedForm URL, contact fields, tags, and metadata.
4. Confirm the lead finishes processing as **Ready**.
5. Verify the resulting conversation and workflow behavior.

Use the source metrics and logs to investigate missing traffic or unexpected volume.

## Disable, rotate, or delete

* **Disable** stops new intake without removing the source.
* **Rotate key** invalidates the current key immediately and creates a replacement.
* **Delete** permanently removes the source and stops its key from working.

Update the posting system immediately after rotating a key. The previous key cannot be restored.

<CardGroup cols={2}>
  <Card title="Implement TrustedForm" icon="file-shield" href="/docs/requiring-trustedform">
    Capture and submit a certificate for every external lead.
  </Card>

  <Card title="Send a lead" icon="paper-plane" href="/docs/sending-leads-to-leadping">
    Choose a payload shape and handle processing results.
  </Card>
</CardGroup>