Social platforms

Search the LinkedIn Ad Library · LinkedIn API

GET/linkedin/search/ads

Search the LinkedIn Ad Library

Request
curl https://api.unifapi.com/linkedin/search/ads \
  -H "Authorization: Bearer $UNIFAPI_KEY"
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 but should still keep one API key, one account balance, and one predictable JSON contract across social, live public-data sources.

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 `billing.records_charged` field matches the number of billable top-level records returned, subject to the one-record minimum.
  • If the workspace balance cannot cover every upstream result, the response can be truncated and `billing.truncated_due_to_balance` tells the caller why.

Billing

Every successful call costs at least one credit. List and search operations charge by billable records returned; single-object lookups charge one record when they succeed. Platform-caused failures can be refunded, and public responses include billing metadata with the credits charged and remaining workspace balance.

Errors and retries

Authentication, validation, rate-limit, not-found, and upstream 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.