Authentication & API Keys

The LeadBoxer API uses API key authentication to secure access to endpoints. All API requests must include a valid API key to authenticate.

Authentication Method

API key authentication is implemented using the x-api-key header. This method provides a simple and secure way to authenticate your requests.

Header Format

Include your API key in the request header as follows:

x-api-key: YOUR_API_KEY

Getting Your API Key

Get a free key

New to LeadBoxer? Get a free key at signup.leadboxer.com. Enter your email and we email you an API key with 25,000 free credits. No app setup needed.

Already have a LeadBoxer account?

  1. Log in to the LeadBoxer app
  2. Go to Integrations → API key
  3. Copy a key, or create a new one with Create key

API keys don't expire. Store your key securely and treat it like a password. If a key leaks, rotate it in the app (see Managing your API keys).

Making Authenticated Requests

Example Request (cURL)

curl -X GET "https://api.leadboxer.com/api/endpoint" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json"

Keep Your API Key Safe

  • Never expose your API key in client-side code, public repositories, or version control
  • Store API keys in environment variables or secure configuration files
  • Use a separate API key for each integration and environment (development, staging, production), so you can rotate one without affecting the others

Error Responses

401 Unauthorized

Returned when the API key is missing or invalid, for example after it was rotated or deleted.

{
  "error": "Unauthorized",
  "message": "Invalid or missing API key"
}

Solution: Verify that your API key is correct and included in the x-api-key header.

Managing your API keys

Manage your keys in the LeadBoxer app under Integrations → API key. Everyone on the account can see and copy the keys; only account admins can create, rename, rotate or delete them.

Several keys per account

An account can have up to 10 API keys. Give each integration its own key, for example "Make", "n8n" or "Production server", so you can replace or remove one without touching the others. All keys use the same account: they share its credits and its rate limits.

The key marked Used by the App is the one the LeadBoxer app itself signs in with. You can rotate it, but not delete it.

Rotating a key

Rotate replaces a key's value. The old value stops working immediately: there is no grace period. Update every app, script, Make or n8n scenario and MCP connection that uses the key straight after rotating it.

To switch without downtime, create a new key, move your integration over to it, then delete the old key.

If you rotate the key used by the app, the app reloads, and teammates who are signed in at that moment need to sign in again.

Deleting a key

Delete removes a key at once. Anything still using it gets 401 Unauthorized. This cannot be undone.

Notifications

The owners and admins of the account get an email whenever a key is created, rotated or deleted, with who did it and when. The email never contains the key itself.

Support

If you encounter authentication issues or need assistance:

  • Check the API status page
  • Review the troubleshooting guide
  • Contact support at [email protected]
  • Visit our community forums for peer assistance

Did this page help you?