Social platforms

Search LinkedIn Ad Library ads · LinkedIn API

GET/linkedin/ads/search
$min $0.003

Searches the LinkedIn Ad Library by advertiser, keyword, country and date range. Paginate with `cursor`.

Using ChatGPT, Claude Code or another client? See the setup steps

Request
curl https://api.unifapi.com/linkedin/ads/search \
  -H "Authorization: Bearer $UNIFAPI_KEY"

Parameters

companyquery
Company name to search for in the LinkedIn Ad Library.
keywordquery
Keyword or phrase to search for in LinkedIn Ad Library ads.
company_idquery
LinkedIn company id to search for in the Ad Library.
countriesquery
Optional comma-separated list of country codes (for example US,CA,MX).
start_datequery
Optional start date filter in YYYY-MM-DD format.
end_datequery
Optional end date filter in YYYY-MM-DD format.
cursorquery
Opaque pagination cursor from a previous response's `pagination.next_cursor`. Omit for the first page.
The parameter for this LinkedIn operation. Use the URL-visible slug or id described in the docs.
Overview

This operation is part of the LinkedIn API in the social platforms category. It uses the same Bearer token, request tracing, error model, and billing envelope as every UnifAPI endpoint, so agents can switch between platforms without custom per-vendor glue code.

Use it when a workflow needs LinkedIn public data alongside other social networks, but should still keep one API key, one account balance, and one predictable JSON contract.

Common agent workflows

  • Search LinkedIn for public mentions, creators, posts, or topics matching a user query.
  • Feed ranked LinkedIn results into research, monitoring, and enrichment workflows.
  • Give an AI agent a stable LinkedIn data source without building a per-platform integration.
  • Normalize LinkedIn responses into the same UnifAPI envelope used across the catalog.
Response shape

Unified envelope, platform-native fields

  • List-style responses return `data` as an array of top-level records plus optional `pagination` for continuation tokens or cursors.
  • The operation has a 3 credits ($0.003) minimum charge, so `billing.records_charged` can be higher than the visible records returned.
  • If the workspace balance cannot cover every result, the response can be truncated and `billing.truncated_due_to_balance` tells the caller why.

Response status codes

200400401402404429500502503

Billing

This operation charges 1 credit per billable record, with a 3 credits ($0.003) operation minimum. Public responses include billing metadata with credits charged, records charged, and remaining workspace balance. Incorrect Credit deductions caused by platform failures can be restored as billing corrections.

Errors and retries

Authentication, validation, rate-limit, not-found, and provider errors use the unified UnifAPI error format. Agents should log `request_id`, retry only retryable failures, and treat invalid API keys, disabled keys, and expired keys as the same public `unauthorized` error type.

Response fields

Fields on each record in data

A successful Search LinkedIn Ad Library ads call returns data as an array; each record carries these fields (12 of 14 shown — the docs list the full schema).

idstring | null
Stable identifier for the ad.
urlstring | null
Public LinkedIn Ad Library URL for this ad when available.
descriptionstring | null
Primary ad body text when available.
headlinestring | null
Ad headline when available.
ad_typestring | null
Ad format type when available.
creative_typestring | null
Raw LinkedIn creative type code when available, for example SPONSORED_STATUS_UPDATE, SPONSORED_VIDEO, SPONSORED_INMAILS or JOBS_V2. Finer-grained than adType and not a closed set.
posterstring | null
Poster name shown on the ad when available.
poster_titlestring | null
Poster title shown on the ad when available.
promoted_bystring | null
Promoted-by attribution when available.
advertiserobject | null
Advertiser summary for this ad.
targetingobject | null
Targeting summary for this ad.
creativeobject | null
Creative content for this ad.
Related endpoints

More LinkedIn operations

Combine endpoints from the same platform, then join the results with other UnifAPI categories without changing authentication or response parsing.