---
title: "Pause a LinkedIn campaign (ad set)"
method: POST
path: "/api/v1/tools/linkedin_pause_campaign/execute"
tags: ["LinkedIn Ads"]
---

# Pause a LinkedIn campaign (ad set)

`POST /api/v1/tools/linkedin_pause_campaign/execute`

## Request

- Base URL: `https://adako.ai`
- URL: `https://adako.ai/api/v1/tools/linkedin_pause_campaign/execute`
- Auth: HTTP bearer

Stops delivery on one campaign (an ad set in Campaign Manager) by setting it to PAUSED. Spend stops; nothing is deleted, the creatives and history stay, and linkedin_resume_campaign starts it again.
Use when: the user has explicitly asked to stop something and you have shown them what it is currently spending and producing.
Do not pause on a few days of data. LinkedIn's B2B volumes are small and a week is the minimum honest window — show last_7_days from linkedin_get_campaign_performance, or last_30_days for anything involving cost per lead, and let the user decide.
Do not pause a campaign that reports no conversions until linkedin_list_conversions confirms a rule is attached: an untracked campaign looks identical to a failing one.
Do not use pausing as deletion. Pausing is reversible; nothing in this adapter deletes a campaign at all.
Returns the campaign read back from LinkedIn, which is how you confirm the pause applied rather than reporting an intention as a fact.

## Headers

- `Idempotency-Key` string

## Request body

- object
  - `arguments` object, required
    - `ad_account_id` string: LinkedIn ad account id — the numeric id from Campaign Manager, as a string ("506699162"). Omit it to use the primary account; pass it when the user manages several.
    - `campaign_id` string, required: The campaign to act on. LinkedIn ids are numeric strings; a full urn:li:… value is also accepted.
    - `idempotency_key` string: Optional caller-supplied key; identical keys never execute twice.
    - `raw_data` boolean: Return compact JSON only (no markdown). Use when you will compute on the result.

## Response `200`

The tool ran. A write returns proposal_id and approve_url while the change waits for approval.

- SuccessEnvelope
  - `success` unknown, required
  - `tool` string, required
  - `data` object, required: Machine-readable result.
  - `markdown` string, required: The same result written for a person or a model.
  - `quota` Quota: Task usage for the current billing period.
    - `plan` string
    - `used` integer
    - `limit` integer
    - `period_end` string
    - `upgrade_url` string
  - `proposal_id` string: Present for writes. Nothing changes on the ad platform until it is approved.
  - `approve_url` string: Where a person approves the proposal.
  - `request_id` string, required

## Other responses

- `400`: Invalid arguments, or the ad account could not be resolved.
- `401`: Missing, invalid, revoked or expired API key.
- `402`: Monthly task quota used up, or the plan does not include this tool.
- `403`: The connected ad account lacks the access level this tool needs.
- `404`: Unknown tool name.
- `409`: Not connected, reconnect needed, confirmation required, a proposal already pending or no longer pending, an identical create that failed earlier today (proposal_failed_before), a create that duplicates an approved one (duplicate_create), the ad-account limit of the plan reached (account_limit), or an Idempotency-Key reused with different arguments.
- `429`: Rate limited by Adako or by the ad platform. See Retry-After.
- `500`: Unexpected error inside Adako.
- `502`: The ad platform returned an error.

---

[API](https://skmtc.dev/adako/apis/adako-rest-api.md) · [All operations](https://skmtc.dev/adako/apis/adako-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/adako/apis/adako-rest-api/revisions/59ee60d48a56?raw)