LinkedIn · Ads

LinkedIn Ad Library Search Scraper API

The LinkedIn Ad Library Search endpoint is one API call: send either a company, a keyword or a company ID with your HProxy key and get back a clean, structured JSON object. Search the LinkedIn ad library by keyword and get live ad creatives back with the advertiser and the dates each ran. HProxy runs the proxies, sessions, anti-bot handling and parsing server-side, so there is no headless browser to babysit and no parser to keep fixing when LinkedIn changes its markup. You only ever touch the JSON.

Get your API key LinkedIn API reference

0.15¢ per call
$1.49 per 1,000
Takes either a company, a keyword or a company ID
Errors and timeouts are not charged

On LinkedIn

Profiles2 Posts and media2Ads2

Ads

Facebook

Google

The call

One GET, and the ad library search comes back as JSON.

Your key goes in one header. 1 required parameter, and the answer is the object below it.

The full reference

curl "https://hproxy.com/api/v1/scrape/linkedin/ad-search?company=value" \
  -H "X-API-Key: hpx_your_key_here"

Response200 OK · JSON

{
  "advertiser": { "name": "Brand Inc", "pageId": "104..." },
  "creatives": [
    { "format": "video", "body": "Shop the new drop", "media": "https://.../ad.mp4" }
  ],
  "spend": { "min": 5000, "max": 10000, "currency": "USD" },
  "dates": { "firstSeen": "2026-06-30", "lastSeen": "2026-07-17" }
}

What comes back

The LinkedIn ad library search object.

creatives[]: Each active ad's media, copy and format.
advertiser: The page or advertiser running the ad.
spend / impressions: Spend range and reach where disclosed.
dates: First-seen and last-seen run dates.

What it takes

Parameters.

Send any one of company, keyword, companyId. company, keyword, or companyId required

companystringvalue

The company parameter.

keywordstringvalue

The keyword parameter.

companyIdstring1234567890

Identifier from a previous response.

countriesstringvalue

Numeric filter applied to the results.

startDatestring2026-07-01

Filter by date, as YYYY-MM-DD.

endDatestring2026-07-01

Filter by date, as YYYY-MM-DD.

paginationTokenstringvalue

The paginationToken parameter.

How it works

Scraping LinkedIn ad library search, in three steps.

You write one line. Proxies, anti-bot walls, rendering and parsing happen on our side.

Create a free account Every LinkedIn endpoint

1
Create a free account
Sign up and top up any amount. The balance pays for every HProxy product.
2
Grab your API key
One key from the dashboard authenticates every scraper.
3
Call the endpoint
Send the GET you need and read the JSON. That is the entire integration.

What people build with it

Where the LinkedIn ad library search endpoint earns its keep.

Spy on competitor ad creatives and messaging.
Track ad spend and campaign timing in your niche.
Build a swipe file of what is running right now.

LinkedIn ad library search questions

Answered before you ask.

The reference

Send one authenticated HTTPS request to the LinkedIn Ad Library Search endpoint with either a company, a keyword or a company ID and your HProxy API key. Search the LinkedIn ad library by keyword and get live ad creatives back with the advertiser and the dates each ran. No proxies, no headless browser and no parsing on your side. The response is ready-to-use JSON.

This endpoint is 0.15¢ per successful call, which is $1.49 per 1,000. It bills from your HProxy balance with no subscription and no monthly minimum. Errors are retried and never charged; a lookup whose target does not exist counts as a call.

The API only accesses publicly available LinkedIn data, the same pages anyone can open in a browser. You are responsible for using the data in line with applicable laws and LinkedIn's terms for your use case.

A structured JSON object with the full ad library search data LinkedIn exposes publicly. See the fields listed above. The schema is consistent across calls, so you integrate once and rely on it.

No. Every call runs on HProxy's own residential network behind the scenes, so requests look like real users. The proxy layer is already included in the per-call price.

Docs and AI

Connect your scraper to an AI, any time.

The whole Scraper API is published as markdown, so an assistant reads every endpoint, every parameter and a real response without a key and writes your integration. And because a scrape is one GET that answers in JSON, an agent can run the scraper itself, on its own schedule, with your key.

Read the scraper docs Set up your assistant

Claude, ChatGPT, Cursor, Gemini, Copilot, Windsurf, Perplexity, Ollama and any assistant that speaks MCP.

The API as markdown

Paste /llms/scraper-api.txt into Claude, ChatGPT, Cursor or Copilot: every endpoint and the whole catalog, in one file. No key and no account to read it.

Open the markdown

An agent can call it

One GET with your key returns structured JSON, so an agent scrapes on its own schedule. No browser to drive, no parser to keep alive between runs.

See the endpoints

MCP server and CLI

Built by us for the free tools and hosted at mcp.hproxy.com: the proxy list, the checker and the IP lookup as tools in Claude, ChatGPT, Cursor or any assistant that speaks MCP. Nothing to install, no key.

Add it to your assistant