# LeadConnector API

> LeadConnector API is the REST API of the LeadConnector platform (ad-publishing, affiliate-manager, agent-studio, associations, blogs, brand-boards, businesses, calendars, campaigns, chat-widget, companies, contacts, ...). This is an LLM-friendly index of its reference documentation, generated from the OpenAPI specs at build time.

- Base URL: https://services.leadconnectorhq.com (append the endpoint path).
- Every request must send a `Version` header whose value is the API version name, e.g. `Version: v3`. Published versions: v3 (latest).
- Every authenticated request sends `Authorization: Bearer <token>`.

## Authentication

- OAuth 2.0 access token: issued to an app through the authorization-code flow ([POST /oauth/token](https://marketplace.leadconnectorhq.com/docs/leadconnector/oauth/get-access-token.md) exchanges the code or a refresh token). A token is issued either for a Sub-Account (location) or for an Agency (company).
- Private Integration Token (PIT): a static token created in the Sub-Account or Agency settings with a chosen set of scopes; it is sent exactly like an access token. Endpoints marked "OAuth access token only" reject PITs.
- Sub-Account vs Agency: every endpoint states which token type it accepts. An Agency access token can be exchanged for a Sub-Account token with [POST /oauth/location-token](https://marketplace.leadconnectorhq.com/docs/leadconnector/oauth/get-location-access-token.md).
- Scopes: every endpoint lists the scopes it requires; the token must carry all of them (requested during OAuth authorization, or selected when the PIT is created).

## Instructions for LLMs

- Default to the latest version, v3, unless the user names another version.
- Always send `Version: <version>` with the version whose documentation you used (`Version: v3` for the latest). Never mix endpoints or schemas from different versions in one integration.
- Call https://services.leadconnectorhq.com followed by the endpoint path; replace `{param}` placeholders with path parameter values.
- Pick the token type, OAuth/PIT method and scopes from the endpoint's Auth line.
- Find endpoints in the version's llms.txt, then read the service `.md` file or the endpoint `.md` file for the full request and response schema.

## API versions

- [v3 (latest) index](https://marketplace.leadconnectorhq.com/docs/llms/v3/llms.txt): services and endpoints of version v3 with links (690 endpoints, ~44k tokens)
- [v3 (latest) full reference](https://marketplace.leadconnectorhq.com/docs/llms/v3/llms-full.txt): every endpoint of version v3 in one compact file, ~657k tokens

## Guide pages

- [Country List](https://marketplace.leadconnectorhq.com/docs/other/country.md)
- [LeadConnector MCP Server](https://marketplace.leadconnectorhq.com/docs/other/mcp.md)

## Optional

- [Full reference of the latest version](https://marketplace.leadconnectorhq.com/docs/llms-full.txt): same content as the v3 full reference