> For the complete documentation index, see [llms.txt](https://help.leadboxer.com/leadboxer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.leadboxer.com/leadboxer/platform-and-api/developer-portal.md).

# Developers & API

LeadBoxer App is built on the **LeadBoxer Platform**: the same tracking, identification and enrichment, available through APIs for your own products, websites and workflows. Developer documentation lives on [developers.leadboxer.com](https://developers.leadboxer.com); this page only covers what you need from the App.

***

### The three APIs

* **Track API**: send website, server-side and email events into LeadBoxer.
* **Lookup API**: identify the company behind an IP address, enrich a company domain, or turn a work email into a professional profile.
* **App API**: read your leads and accounts, and manage tags, owners, segments, datasets and users.

See [When to use which API](https://developers.leadboxer.com/docs/when-to-use-which-api) for details.

### Get your API key

API keys are generated from your LeadBoxer account:

1. Log in to [LeadBoxer App](https://app.leadboxer.com). No account yet? [Create a free one](https://app.leadboxer.com/sign-up).
2. Go to [Integrations → Data → API key](https://app.leadboxer.com/integrations-connectors/data/api-key).
3. Copy the key and send it in the `x-api-key` header of every request.

{% hint style="warning" %}
Treat your API key like a password. Never put it in your website's JavaScript or in a public repository: call the API from your server instead.
{% endhint %}

API calls that identify or enrich data use the same credits as the App. The first 25,000 credits each month are free. See [LeadBoxer for developers](https://www.leadboxer.com/developers) and [pricing](https://www.leadboxer.com/pricing).

### Useful links

* [Quickstart](https://developers.leadboxer.com/docs/quickstart)
* [API reference](https://developers.leadboxer.com/reference)
* [Credit cost per endpoint](https://developers.leadboxer.com/docs/credit-usage-cost-model) and [rate limits](https://developers.leadboxer.com/docs/credits-rate-limits)
* [API changelog](https://developers.leadboxer.com/changelog)
* [MCP server for AI assistants](/leadboxer/platform-and-api/mcp-server.md)
* [n8n and Make automation](https://www.leadboxer.com/integrations/automation), plus our guides for [Zapier](/leadboxer/integrations/other/how-to-get-started-with-leadboxer-on-zapier.md), [make.com](/leadboxer/integrations/other/make.com.md) and [n8n](/leadboxer/integrations/other/n8n.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.leadboxer.com/leadboxer/platform-and-api/developer-portal.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.