canonical: https://jentic.com/apis/adyntel.com/adyntel

# Adyntel API

Jentic publishes the only available OpenAPI specification for Adyntel API, keeping it validated and agent-ready. Adyntel is an ad intelligence service that scrapes and surfaces competitor advertising creative across the Facebook/Instagram ad library, Google Ads transparency centre, and LinkedIn ad library through a single REST endpoint per platform. Each call returns structured ad records - creative copy, media URLs, advertiser metadata, and run dates - so teams can monitor competitor campaigns without manually browsing each platform's ad library. The API exposes three POST operations, one per platform, all authenticated with an X-API-Key header.

## For AI agents

Pull competitor ad creative and metadata from the Facebook, Google, and LinkedIn ad libraries to feed market-intelligence and creative-research workflows.

## Scope

Does not handle ad placement, billing, or campaign management - use for reading competitor ad creative from public ad libraries only.

## Capabilities

- Scrape competitor ads from the Meta (Facebook and Instagram) ad library by advertiser or keyword
- Pull live and archived ad creative from the Google Ads transparency centre
- Retrieve LinkedIn ad library results for a target company or industry
- Capture ad copy, media URLs, advertiser names, and run dates in one structured payload
- Feed competitor creative into spreadsheet, BI, or LLM-driven creative-analysis pipelines

## Use cases

### Competitor Ad Monitoring

Track which ads competitors are running across Meta, Google, and LinkedIn from a single integration. Adyntel queries each platform's public ad library on demand and returns structured ad records - creative URLs, copy, advertiser, and run dates - so a marketing team can review competitor activity in their own dashboard or notebook instead of manually scrolling each library. Refresh as often as needed; the three POST endpoints accept advertiser or keyword filters.

Example prompt: Call POST /facebook with the competitor's page name and return the ad copy and creative URLs of all currently running ads

### Creative Research and Inspiration

Pull thousands of live ad creatives from the three biggest paid channels to seed a creative review or to fine-tune a generative model. Each platform endpoint returns the ad media URL, headline and body copy, and advertiser metadata, which can be piped directly into an asset library, prompt set, or analysis spreadsheet. Useful for agencies and growth teams running creative iteration sprints.

Example prompt: Call POST /google with a list of three advertisers and consolidate the headline, description, and final URL of every returned ad into a single CSV

### Market Intelligence Reports

Generate a recurring report comparing your brand's ad activity against named competitors across all three platforms. Adyntel returns the structured records needed to count active ads, identify creative themes, and detect new campaign launches. Combine with a scheduler to produce weekly or monthly intelligence briefs with no manual data collection.

Example prompt: Pull last 30 days of ads for five named competitors from /facebook, /google, and /linkedin and produce a markdown summary grouped by platform

### AI Agent Ad-Library Lookup

Give an AI agent the ability to answer ad-library questions in conversation. Through Jentic, an agent searches for the right Adyntel operation by intent, loads the schema, and executes the call with the user's API key isolated in your Jentic One instance. The agent never sees the raw key and the operation runs in under a second per platform.

Example prompt: Search Jentic for 'find competitor facebook ads', load the /facebook schema, and execute with advertiser=Nike to return the top 10 active ads

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /facebook | Scrape competitor ads from the Meta (Facebook and Instagram) ad library |
| POST | /google | Pull ads from the Google Ads transparency centre |
| POST | /linkedin | Retrieve ads from the LinkedIn ad library |

## Key resources

- **Facebook** — Scrape competitor ads from the Meta ad library covering Facebook and Instagram placements
- **Google** — Pull ad records from the Google Ads transparency centre by advertiser
- **LinkedIn** — Retrieve ads from the LinkedIn ad library for a target company or campaign

## Why Jentic

- **Setup:** Wiring the Adyntel API by hand means learning its API-key header and coding a request per ad platform. Through Jentic you install once, import the Adyntel API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Adyntel takes the target platform in the request body across its Facebook, Google, and LinkedIn operations, so limit the agent to the operations it needs, such as reading Facebook ad creative. You choose which platform operations are in the allowed set, so the others are not reachable unless you add them.
- **Credential handling:** Your Adyntel X-API-Key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'find competitor Facebook ads', and Jentic returns the matching Adyntel operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Facebook Graph API** — Official Meta API for managing your own ads, pages, and audiences
- **Semrush API** — Broader competitive intelligence covering paid and organic search and display
- **Apify** — General scraping platform with prebuilt actors for ad library extraction

## FAQ

### Why is there no official OpenAPI spec for Adyntel API?

Adyntel does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Adyntel API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Adyntel API use?

Adyntel uses an API key sent in the X-API-Key request header on every call. Through Jentic, the key is stored encrypted in the vault and injected at execution time, so the agent's context never contains the raw secret.

### Can I scrape Facebook, Google, and LinkedIn ads with the Adyntel API?

Yes. Adyntel exposes one POST endpoint per platform - /facebook, /google, and /linkedin - each returning structured ad records including creative URLs, copy, advertiser, and run dates. All three platforms are covered by the same API key.

### What are the rate limits for the Adyntel API?

Adyntel does not publish rate limits in the spec; check https://docs.adyntel.com/ for the limits attached to your plan. Through Jentic, agents receive structured 429 responses if a platform-specific quota is hit so retries can be backed off.

### How do I pull competitor Facebook ads through Jentic?

Run pip install jentic, search Jentic with the query 'find competitor facebook ads', load the /facebook schema, and execute it with the advertiser name in the body. Jentic returns the parsed ad records without exposing your API key.

### Does the Adyntel API return historical or only live ads?

Adyntel returns the records currently surfaced by each platform's own ad library, which includes live ads and any archived ads still kept by Meta, Google, or LinkedIn. Coverage of older creatives depends on what each platform retains in its public library.

### Can I limit what my agent is allowed to do with the Adyntel API?

Yes. Because Jentic One is self-hosted, you define the rules that decide which Adyntel operations your agent may call, so you can allow only the platform endpoints it needs, such as the Facebook ad-library read, while leaving the Google and LinkedIn operations out of the allowed set. The agent cannot reach an operation you have not added, and only the credential you store is injected at execution time so the raw X-API-Key never enters the agent's context. This lets you scope the agent to reading competitor ad creative from one platform without granting access to the others.