Which APIs support LinkedIn ad research?
Which APIs support LinkedIn ad research? Follow concrete contracts, examples and reviewable steps using LinkedIn.
Copy the agent prompt manually
Answer
Start by inspecting the contracts and local samples for LinkedIn Ad Library search, LinkedIn ad detail. Establish the input for linkedin.ads.search, then check whether its ad object contains the fields your task needs.
Document the input scope, sampling rule and intended use, and preserve request IDs and missing-field markers. An API supplies the contracted sample; interpretation still requires checks of context and representativeness.
Relevant contracts
| Capability | Object | Shape | Pagination |
|---|---|---|---|
| linkedin.ads.search | Ad | items | Explicit cursor |
| linkedin.ads.get | Ad | item | No cursor |
Input contract
Inspect meanings, examples and conditional rules for the selected method. view and fields control the response without changing the TEST unit price.
- GET: supply exactly one of query / advertiser.
| Method | Field | Type | Requirement | Meaning | Enum or bound | Example |
|---|---|---|---|---|---|---|
| GET | query | string | Optional / conditional | Search terms | — | "cloud security" |
| GET | advertiser | string | Optional / conditional | Only the ads of this company, by its name; not with query. Ads of the company's other pages (its developers' page, say) may be among them | — | — |
| GET | region | string | Optional / conditional | Only ads delivered in this country or region, by its two-letter code; all of them when left out | — | — |
| GET | cursor | string | Optional / conditional | The `next_cursor` of the previous page. A new page is a new call. | — | — |
| GET | view | string | Optional / conditional | How much of each item: compact (the most used fields, long text cut short), standard, or full (adds `ext`). | ["compact","standard","full"] | — |
| GET | fields | array | Optional / conditional | Return only these fields of each item, by path (`author.name`). | maxItems: 64 | — |
Complete one verification
Run one local fixture for a listed capability and inspect the object structure. Then filter, classify or export according to the question. A local sample cannot replace evidence for a real-platform conclusion.
{
"capability": "linkedin.ads.search",
"method": "GET",
"params": {
"query": "cloud security"
}
}Clear inputs. Inspectable output.
Each click runs a local fixture. Advanced JSON inputs are checked against the selected method. Editing does not execute a request.
Copying does not execute. CLI quote is read-only and needs a local customer TEST key. Configure MCP in demo mode first. GET and POST batches both return only fictional local fixtures.
Download contract example (no execution) ↗For TEST budgets, Key scopes or failure scenarios, open the account console. Customer sandbox ↗