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

# API v2

> The LinkedCamp API: 133 endpoints for campaigns, sequences, leads, the inbox, AI agents, analytics and more.

API v2 is the LinkedCamp API. Build and launch campaigns, write their sequences, manage leads, work the inbox, run AI reply agents, schedule LinkedIn posts and pull analytics, all over HTTP with your API key.

```text Base URL theme={null}
https://api.linkedcamp.com/v2
```

> [card] [133 endpoints](#endpoints)
>
> 64 read-only, 69 write and 28 destructive.

> [card] [Same API key](#authentication)
>
> The key you already use for v1.

> [card] [OpenAPI](https://api.linkedcamp.com/v2/openapi.json)
>
> The full spec, for code generators and API clients.

> [!NOTE]
>
> [API v1](https://docs.linkedcamp.com/api-reference/overview.md) keeps working unchanged. It is now the legacy API: new endpoints ship in v2.

## Authentication

Send your API key in the `X-Api-Key` header, or as a bearer token. It is the same key as v1, from [Settings → Integrations → API](https://app.linkedcamp.com/settings/integrations?type=api). API access needs a plan with Pro features (Pro or Agency) and the **Integrations** permission.

```bash theme={null}
curl -X POST https://api.linkedcamp.com/v2/whoami \
  -H "X-Api-Key: YOUR_API_KEY"
```

`Authorization: Bearer YOUR_API_KEY` works too, and so does v1's `token` header, so moving an integration from v1 is a URL change. Keys in the query string are not accepted.

> [!WARNING]
>
> The key acts as you. Anyone who has it can launch campaigns and send messages from your account. Keep it on your server, never in a browser or mobile app.

## Making a request

Every endpoint is a `POST` to `/{tool_name}`, with the tool's arguments as a JSON object. Leave the body empty, or send `{}`, for a tool that takes no arguments.

```bash theme={null}
curl -X POST https://api.linkedcamp.com/v2/campaign_list \
  -H "X-Api-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"status": "ACTIVE"}'
```

Each endpoint page lists its arguments. Unknown or invalid arguments are refused with a `400` that names the field.

## Responses

A successful call returns `200` with the tool's result as JSON. Reads return the data itself. Writes return a confirmation and, usually, the record:

```json campaign_set_status theme={null}
{
  "ok": true,
  "message": "Sending is halted. Pending steps stay queued and resume where they left off.",
  "data": {
    "campaignId": "665f1c2a9b3e4d0012ab34cd",
    "status": "PAUSED",
    "note": "The change is recorded in `campaign_logs`."
  }
}
```

A failed call returns an error object with a status code. See [Errors](https://docs.linkedcamp.com/api-v2/errors.md).

## Endpoints

Endpoints are grouped in the sidebar by the kind of record they work on: campaigns, sequences, leads, tags, conversations, templates and so on. Each one is tagged:

| Kind | What it means |
| - | - |
| **Read-only** | Changes nothing. Safe to call and retry. |
| **Write** | Changes data in your account. |
| **Destructive** | Sends, publishes, launches or deletes. Get a person to confirm before your code calls it. |

Destructive endpoints include `campaign_launch`, `message_send`, `campaign_send_test_email`, `post_upsert`, `flow_set` and every `_delete`. A launched campaign or a sent message cannot be undone.

Your plan and permissions decide which endpoints you can call. An endpoint your plan does not include answers `403`. Call `whoami` to see your plan and permissions.

## Building a campaign

A campaign is built in six calls:

1. `campaign_create` makes a draft.
2. `campaign_set_source` sets the audience. `search_url_build` builds a LinkedIn or Sales Navigator search URL from criteria.
3. `campaign_update` attaches the sending account, schedule and daily limits.
4. `flow_set` writes the sequence: connection requests, messages, emails, waits and branches.
5. `campaign_get` reports anything still blocking launch.
6. `campaign_launch` starts sending.

Call `reference` for the exact status values, step types and field names the other endpoints accept.

## Moving from v1

* Change the base URL to `https://api.linkedcamp.com/v2` and call the matching endpoint. The API key stays the same.
* v2 has no webhook endpoints. Keep using the [v1 webhooks](https://docs.linkedcamp.com/api-reference/webhooks/create-webhook.md), or use the automation endpoints.
* Sub-account management (register, pause, resume, cancel, tokens) stays on v1. In v2, `subaccount_list` lists your agency's accounts.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.