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

# Authentication

> All requests to the Leadhub Leadhub API require an API Key.

## API Key

Every request must include your API Key in the `apikey` header:

```http theme={null}
apikey: your_api_key_here
```

<Note>
  Contact your Leadhub account manager to obtain your `publisher_id` and API Key.
</Note>

## Example

```bash theme={null}
curl -X POST https://{tenant}.techea.eu/api/v1/lead \
  -H "apikey: your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{ ... }'
```

## Advertiser authentication

Advertisers use a separate API Key to call `PATCH /lead/{lead_id}/status`. This key is provisioned by Leadhub when your integration is set up.

## Security

* Keys are sent in headers, never in URLs or query strings.
* Keys do not expire by default. Contact Leadhub to rotate a compromised key.
* Each key has a fixed scope — publisher keys cannot call advertiser endpoints and vice versa.