Fetch & parse a domain's ads.txt
API · /adstxt-api
ads.txt API
Fetch and evaluate any publisher's ads.txt / app-ads.txt — the IAB authorized-digital-sellers standard. Pass a domain and the check endpoint fetches its ads.txt server-side, then returns every seller record parsed into its fields — advertising system, the publisher's seller/account id, the DIRECT or RESELLER relationship and the optional certification-authority id (TAG-ID) — alongside counts (direct, reseller, distinct ad systems) and the declared variables OWNERDOMAIN, MANAGERDOMAIN, CONTACT and SUBDOMAINS. The verify endpoint answers the one question programmatic-advertising integrations actually ask: is this advertising system, with this publisher id, authorized to sell this domain's inventory? — returning an authorized boolean and the matching records. A missing file is reported as found:false (not an error), and soft-404 HTML pages are detected and rejected so you never parse a "page not found" as records. The request is made server-side and private or internal targets are refused (SSRF-guarded). Built for ad-tech supply-chain verification, SSP/DSP onboarding checks, anti-fraud and inventory audits. An ads.txt seller-authorization checker — distinct from the security-contact file reader (securitytxt), the robots.txt crawlability evaluator (robots) and the sitemap parser (sitemap). No upstream key, no cache.
API salute
salutare- Tempo di attività
- 100.00%
- Sondaggi del server · 24 ore su 24
- Latenza media
- 155 ms
- Sondaggi del server · 24 ore su 24
- Abbonati
- 4,867
- attiva
- Chiamate totali
- 57
- ultimi 7 giorni
Prezzi
Scegli un livello: fatturazione mensile, annullamento in qualsiasi momento.
Free
Gratis
- 2,090 chiamate/mese
- 2 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 2,090 llamadas/mes
- 2 solicitudes/seg
- Verificar + comprobar
- Sin tarjeta de crédito
Starter
€6.15 /mese
- 40,000 chiamate/mese
- 8 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 40k calls/month
- 8 req/sec
- Full record + variable parsing
- Email support
Pro
€20.25 /mese
- 212,000 chiamate/mese
- 20 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 212k calls/month
- 20 req/sec
- Supply-chain verification pipelines
- Priority support
Mega
€52.60 /mese
- 808,000 chiamate/mese
- 50 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 808k calls/month
- 50 req/sec
- Ad-tech platform scale
- Dedicated SLA
Costruito da
Correlato APIs
Altro APIs con tag sovrapposti.
Marketing Metrics API
API de matemáticas de métricas de marketing digital, calculadas local y determinísticamente. El endpoint ads calcula KPIs de campaña a partir de dos de los siguientes: gasto, impresiones, clics y conversiones: el CPM (costo por mil impresiones), el CPC (costo por clic), el CTR (tasa de clics), la tasa de conversión y el CPA (costo por adquisición). El endpoint roas calcula el retorno de la inversión publicitaria, ROAS = ingresos ÷ gasto, el porcentaje de ROI y la ganancia bruta, y — dado un margen bruto — el ROAS de equilibrio de 1 ÷ margen. El endpoint ltv calcula el valor de vida del cliente, valor promedio del pedido × frecuencia de compra × vida útil × margen bruto, y, con el gasto de marketing y el número de nuevos clientes, el costo de adquisición de clientes, la importantísima relación LTV:CAC y el período de recuperación del CAC en meses. Todo se calcula local y determinísticamente, por lo que es instantáneo y privado. Ideal para desarrolladores de aplicaciones de marketing, publicidad, comercio electrónico y crecimiento, paneles de campaña y herramientas de informes, y calculadoras de agencias. Cálculo local puro — sin clave, sin servicio de terceros, instantáneo. En vivo, nada almacenado. 3 endpoints. Esto son matemáticas de métricas de marketing; para matemáticas de porcentajes use una API de porcentajes y para conversión de divisas use una API de divisas.
api.oanor.com/marketing-api
Ad Metrics API
Marketing and advertising metrics as an API — the everyday campaign maths, computed locally and deterministically and entirely currency-agnostic. The funnel endpoint takes any of impressions, clicks, conversions, spend and revenue and computes every metric the inputs allow: click-through rate (CTR), cost per click (CPC), cost per mille (CPM), conversion rate, cost per acquisition (CPA), average order value, return on ad spend (ROAS), return on investment (ROI) and profit — anything not derivable is returned as null rather than guessed. The roas endpoint focuses on profitability: ROAS, ROI and profit, and — given a gross margin — the break-even ROAS and gross profit, with a profitable flag. The target endpoint reverse-plans a campaign: from a conversion or revenue goal and your known rates it works out the required clicks, impressions and budget and the expected revenue and ROAS. Everything is computed locally and deterministically, so it is instant and private. Rates such as conversion_rate and ctr are given as fractions (0.05 = 5%). Ideal for marketing dashboards and reporting, media-buying and bid tools, agency and campaign planners, and e-commerce analytics. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is advertising-metric maths; for loan and investment maths use a finance-calculator API.
api.oanor.com/admetrics-api
Cookie API
Parse and build HTTP cookies. The parse endpoint reads a Set-Cookie header into its name, value and structured attributes — Domain, Path, Expires, Max-Age, Secure, HttpOnly, SameSite, Priority and Partitioned — or, with mode=cookie, splits a request Cookie header like "a=1; b=2; c=3" into an ordered list and a name→value map. The serialize endpoint builds a correct Set-Cookie string from simple fields, with sensible defaults (Path=/), proper date formatting for Expires, optional URL-encoding of the value, and validation of the cookie name, the date and the enum attributes — and it automatically adds Secure when SameSite=None, as browsers require. Everything is computed locally and deterministically, so it is instant and private. Ideal for web frameworks and middleware, API debugging and proxies, session and consent tooling, testing and security review. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This parses and builds cookie strings; it does not fetch a URL — to inspect a live site's response headers use a security-headers or HTTP API.
api.oanor.com/cookie-api
HTTP Status API
Cada código de estado HTTP como una API. Busque cualquier código (p. ej., 404, 429, 503) y obtenga su frase de razón estándar, su clase (1xx Informativo, 2xx Éxito, 3xx Redirección, 4xx Error del Cliente, 5xx Error del Servidor), una descripción en inglés sencillo, la RFC que lo define, y banderas útiles para saber si es un error y si es comúnmente seguro reintentar (408, 425, 429, 500, 502, 503, 504). Liste cada código asignado o filtre por clase, y enumere las cinco clases de estado. Perfecto para clientes y pasarelas de API, páginas de error, paneles de registro y monitoreo, documentación y enseñanza. Cálculo puramente local — sin clave, sin servicio de terceros, instantáneo. En vivo, nada almacenado. 4 endpoints. Distinto de los verificadores de host/tiempo de actividad que reportan un estado en vivo — este es el diccionario de referencia de los códigos en sí.
api.oanor.com/httpstatus-api
Domande frequenti
Risposte rapide su prezzi, quote e integrazione.
Come ottengo una chiave API per ads.txt API?
Qual è il limite di velocità di ads.txt API?
Quanto costa ads.txt API?
Posso cancellare l'abbonamento in qualsiasi momento?
ads.txt API è conforme al GDPR?
Scegli un endpoint dall'elenco a sinistra per visualizzarne i dettagli e provarlo.
Frammenti di codice
Iscriviti per ottenere una chiave API, quindi chiama qualsiasi percorso sotto il tuo slug.
curl https://api.oanor.com/adstxt-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/adstxt-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/adstxt-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
"https://api.oanor.com/adstxt-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())
Valutazioni
Accedi per votare.
Nessuna recensione ancora.
Discussione
Fai domande, condividi consigli, ricevi risposte dal provider e dagli altri sviluppatori. Pubblico — chiunque può leggere.
Accedi per scrivere o rispondere.
AccediNuova discussione
·
-
Risposta del provider
🔒 Discussione bloccata — non si può più rispondere.
-
·
- Nessuna discussione — inizia tu.
Supporto
Supporto privato 1:1 con il provider — fatturazione, integrazione, account. Solo tu e il team del provider vedete questi thread.
Accedi per aprire un ticket di supporto.
AccediApri nuovo ticket
Descrivi cosa ti serve. Il team del provider riceve un'email e risponde sulla pagina del ticket.
-
·
Urgente - Nessun ticket per questa API.