Adyntel / List a company's LinkedIn ads
Adyntel tool adyntel-linkedin on looot: input fields, $0.00642 per call, output shape, and code to run it with curl, JavaScript or Python.
Shows which LinkedIn ads a company is running. Send company_domain or linkedin_page_id (or the plural lists company_domains, linkedin_page_ids); continuation_token pages results. Returns ads with ad_id, advertiser, commentary, creative_type and type. Send one of: company_domain, linkedin_page_id, company_domains, linkedin_page_ids.
- Tool id:
adyntel-linkedin - Provider: Adyntel
- Job: Search the LinkedIn ad library (
ads.linkedin.search) - Price: $0.00642 per call. A call that fails at the provider costs $0.
Inputs
| Name | Type | Required | Description |
|---|---|---|---|
all_ads |
boolean | no | This will automatically use the continuation_token and scrape all the pages, returning all available ads. Works only with a webhook_url as it needs a place to send each page, one by one. Warning: use this cautiously because there is no way of stopping it. If you use this on a domain that runs 10000 ads, it will try to scrape all the ads and it will use the credits (one page = one credit) |
company_domain |
string | no | Company website. Example: “nike.com” |
company_domains |
array | no | Multiple company domains for batch mode |
continuation_token |
string | no | Token used to grab the next set of ads |
data_provider |
string | no | Data provider to use |
extract |
string | no | Extract specific data. Use ‘number_of_ads’ to return only the ad count. |
linkedin_page_id |
string | no | LinkedIn Page ID |
linkedin_page_ids |
array | no | Multiple LinkedIn page IDs for batch mode |
live_ads |
boolean | no | Only return currently active ads |
webhook_url |
string | no | Webhook URL where the data will be returned |
Output
Shape of the run’s result, checked against 1 real answer:
{ ads: { type, ad_id, advertiser: { name, logo_url, promoted }, commentary: { link, text }, creative_type, view_details_link }[], keyword, page_id, countries, total_ads, is_last_page, continuation_token }
Run it
Every call needs your API token in LOOOT_TOKEN; Sign in shows how to get one. Each run also needs a new idempotency key, so a retry never pays twice. With wait: 30 the answer comes back inline when the run ends within 30 seconds. Otherwise you get the running run back: poll GET /v1/runs/<runId>.
Example input with placeholder values:
curl -X POST "https://api.looot.ai/v1/runs" \
-H "Authorization: Bearer $LOOOT_TOKEN" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{"endpointId":"adyntel-linkedin","input":{"company_domain":"nike.com"},"wait":30}'const response = await fetch("https://api.looot.ai/v1/runs", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.LOOOT_TOKEN}`,
"Content-Type": "application/json",
"Idempotency-Key": crypto.randomUUID(),
},
body: JSON.stringify({
endpointId: "adyntel-linkedin",
input: {
company_domain: "nike.com",
},
wait: 30,
}),
});
const run = await response.json();
console.log(run.status, run.result);import os
import uuid
import requests
response = requests.post(
"https://api.looot.ai/v1/runs",
headers={
"Authorization": f"Bearer {os.environ['LOOOT_TOKEN']}",
"Idempotency-Key": str(uuid.uuid4()),
},
json={
"endpointId": "adyntel-linkedin",
"input": {
"company_domain": "nike.com",
},
"wait": 30,
},
timeout=90,
)
run = response.json()
print(run["status"], run.get("result"))To let looot pick among every provider of this job instead, send job:ads.linkedin.search as endpointId; see the job page.