n8n, Clay and no-code

Use AdLib from n8n with the community node, from Clay with an HTTP column, and from Make or Zapier through webhooks.

n8n

Install the community node n8n-nodes-adlib (Settings → Community nodes), add your API key as a credential, and use the AdLib node to resolve domains, search ads, check domains or read advertiser history. To react to competitor changes, point a watchlist's webhook_url at an n8n Webhook trigger.

Clay

Add an HTTP API column:

Method GET, URL https://api.adlibapi.com/v1/domains/{{Domain}}/check
Header X-API-Key with your key

Map data.advertising (true, false, or null when no platform could be checked) and the per-platform results in data.platforms into columns. Each check costs 3 credits; checks where no platform could be reached are free. For larger lists use a batch job of type domains.

Make and Zapier

Use a Webhooks trigger in Make or Zapier ("Catch hook") and put its URL into a watchlist's webhook_url. Each advertiser.changes event arrives as JSON with the new, stopped and changed ads. See Watchlists and webhooks.

Google Sheets and BI tools

Any tool that can call a REST API with a header works. The OpenAPI spec lets you generate a client in most languages.