Facebook Ad Library Company Ads API examples for SocQ

Collect public Facebook Ad Library ads for one advertiser Page ID, returning creative text, media, Page context, delivery details, and visible signals as normalized records.

Try Facebook Ad Library Company Ads API · Get an API key · Documentation · All SocQ examples

Use cases

• Advertiser ad monitoring: Track archive IDs, creative text, media, active state, delivery dates, source URLs, and collected_at for a known advertiser Page.
• Creative and format comparison: Compare text, images or videos, display format, CTA, destination links, and collation context across the Page's returned ads.
• Market-filtered ad review: Run country, language, status, media, and date filters to build separate ad sets for defined market or delivery questions.
• Public signal snapshot reporting: Combine Page identity, Page likes, reach, spend, currency, delivery state, and collected_at when those public values are exposed.

API behavior

• page_id is the required numeric advertiser Page ID returned by Company Search.
• results_limit defaults to 100 and accepts integers from 20 through 2,000.
• Optional filters include country, status, media type, two-letter language, sort order, and delivery dates.
• Returned ads and their public fields can change over time; an empty result does not prove that the Page has never advertised.

All requests use the shared asynchronous flow:

submit -> task_id -> poll task -> read every cursor page -> save results

Quick start

cp .env.example .env
export SOCQ_API_KEY="your-api-key"

Run the complete Node.js workflow:

cd node
npm start

Run the complete Python workflow:

python3 -m pip install -r python/requirements.txt
python3 python/main.py

Both examples load payload.example.json, retry transient API responses, wait for task completion, read every cursor page, and save a paginated public advertiser-ad dataset with creative, delivery, and visible-metric context to output/results.json.

Never expose SOCQ_API_KEY in browser code, mobile apps, public repositories, screenshots, fixtures, or logs.

Request

POST https://api.socq.ai/v1/facebook-ad-library/company-ads
Authorization: Bearer <SOCQ_API_KEY>
Content-Type: application/json

{
  "page_id": "100000000000000",
  "results_limit": 100,
  "country": "US",
  "status": "ACTIVE"
}

The submit response contains data.task_id. Poll the task endpoint until data.status becomes succeeded or failed, then continue with data.results.next_cursor while data.results.has_more is true.

Complete workflow example

The Node.js and Python programs implement the production-shaped happy path:

1. Load and validate configuration.
2. Submit the endpoint-specific payload.
3. Retry rate-pressure and transient server responses with bounded backoff.
4. Poll the asynchronous task with a ten-minute application timeout.
5. Stop cleanly on a failed task and surface the public error message.
6. Read all cursor pages instead of silently returning only the first page.
7. Write a stable JSON artifact containing task metadata and normalized records.

Use the synthetic files in fixtures/ for tests and documentation. They do not contain customer, account, or production data.

Production notes

See docs/production-notes.md for validation, retry, timeout, pagination, deduplication, logging, and endpoint-specific guidance.

Responsible use and platform scope

• Use only publicly accessible Facebook Ad Library ads, advertiser Pages, creative content, delivery context, and visible signals supported by the selected endpoint.
• Do not use the examples to access restricted content, login-only surfaces, authentication controls, or non-public information about advertisers or audiences.
• SocQ is not an official API of the represented social platform and is not affiliated with or endorsed by that platform.
• Before production use, assess the laws, platform terms, privacy obligations, and retention requirements that apply to your organization and use case.
• Collect only the fields needed for a defined purpose, restrict access, set retention periods, and support correction or deletion workflows where required.
• Platform names and trademarks belong to their respective owners.

This section describes the public-data boundary; it is not legal advice or a guarantee that every use case is permitted in every jurisdiction.

Repository contents

Path	Purpose
curl/request.md	Copy-paste submit, poll, and pagination requests
node/index.mjs	Complete Node.js workflow
python/main.py	Complete Python workflow
payload.example.json	Safe endpoint-specific request body
fixtures/	Synthetic submit and task response shapes
docs/production-notes.md	Production integration guidance