> For the complete documentation index, see [llms.txt](https://routelift.gitbook.io/routelift-api-integration/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://routelift.gitbook.io/routelift-api-integration/getting-started/publish-your-docs.md).

# Authentication

We use API keys to authenticate requests to the RouteLift API. Requests without a valid API key will return a `401 Unauthorized` error.

#### Generating API Keys

You can generate secret API keys from your Partner Dashboard. Navigate to:

**Settings → API Keys & Webhooks**

Each key is environment-specific (production or sandbox). You can create multiple keys for different use cases.

#### Secret vs Public Keys

* **Secret keys** should only be used in your backend systems.
* **Never expose your secret keys in frontend code, SDKs, or public repositories.**
* If building a frontend integration, use a limited-scope public key if available.

#### Keeping Your Keys Secure

API keys are unique to your account. If you believe a key has been compromised, you can revoke or regenerate it from your dashboard at any time.

#### Authorization Method

Use HTTPS and include your secret key in the `Authorization` header of every request:

```
Authorization: Bearer {YOUR_SECRET_KEY}
```

Example:

```
curl -X GET https://integrations.routelift.com/v1/deliveries \
  -H "Authorization: Bearer sk_test_abc123"
```