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

# Introduction

> Programmatic access to Leadpipe identification, visitor data, and pixel management

The Leadpipe Identification API gives you programmatic access to resolved visitor data and full control over your tracking pixels.

## Base URL

```bash theme={null}
https://api.aws53.cloud
```

## Authentication

All requests require an `X-API-Key` header with your organization API key.

```bash theme={null}
curl https://api.aws53.cloud/v1/data \
  -H "X-API-Key: sk_..."
```

Get your API key from **Settings > API Keys** in the dashboard.

## Pixel API

The pixel endpoints let you:

* list all pixels for your organization
* create a pixel and receive the embed `code` snippet
* pause or activate a pixel
* manage path filters with `includedPaths` or `excludedPaths`

Path filters support two mutually exclusive modes:

* `includedPaths`: allowlist mode, where the pixel fires only on matching path prefixes
* `excludedPaths`: denylist mode, where the pixel fires everywhere except matching path prefixes

The live API also returns:

* `pausedReason` when listing pixels
* `code` when creating a pixel

Use the generated endpoint pages under **Pixels** for the exact request and response schema.

## Errors

| Status | Description                              |
| ------ | ---------------------------------------- |
| `401`  | Missing or invalid API key               |
| `403`  | API key revoked or organization inactive |
| `409`  | Pixel already exists for this domain     |
| `503`  | Service unavailable                      |