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 health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 155 ms
- Server probes · 24h
- Subscribers
- 4,867
- active
- Total calls
- 57
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 2,090 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 2,090 calls/month
- 2 req/sec
- Check + verify
- No credit card
Starter
€6.15 /month
- 40,000 calls / month
- 8 requests / second
- Hard cap (429 above quota, no overage)
- 40k calls/month
- 8 req/sec
- Full record + variable parsing
- Email support
Pro
€20.25 /month
- 212,000 calls / month
- 20 requests / second
- Hard cap (429 above quota, no overage)
- 212k calls/month
- 20 req/sec
- Supply-chain verification pipelines
- Priority support
Mega
€52.60 /month
- 808,000 calls / month
- 50 requests / second
- Hard cap (429 above quota, no overage)
- 808k calls/month
- 50 req/sec
- Ad-tech platform scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Marketing Metrics API
Digital-marketing metrics maths as an API, computed locally and deterministically. The ads endpoint computes campaign KPIs from any two of the spend, impressions, clicks and conversions: the CPM (cost per thousand impressions), the CPC (cost per click), the CTR (click-through rate), the conversion rate and the CPA (cost per acquisition). The roas endpoint computes the return on ad spend, ROAS = revenue ÷ spend, the ROI percentage and the gross profit, and — given a gross margin — the break-even ROAS of 1 ÷ margin. The ltv endpoint computes the customer lifetime value, average order value × purchase frequency × lifespan × gross margin, and, with the marketing spend and number of new customers, the customer acquisition cost, the all-important LTV:CAC ratio and the CAC payback period in months. Everything is computed locally and deterministically, so it is instant and private. Ideal for marketing, advertising, e-commerce and growth app developers, campaign dashboards and reporting tools, and agency calculators. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is marketing-metrics maths; for percentage maths use a percentage API and for currency conversion use a currency API.
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
Every HTTP status code as an API. Look up any code (e.g. 404, 429, 503) and get its standard reason phrase, its class (1xx Informational, 2xx Success, 3xx Redirection, 4xx Client Error, 5xx Server Error), a plain-English description, the RFC that defines it, and handy flags for whether it is an error and whether it is commonly safe to retry (408, 425, 429, 500, 502, 503, 504). List every assigned code or filter by class, and enumerate the five status classes. Perfect for API clients and gateways, error pages, logging and monitoring dashboards, documentation and teaching. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. Distinct from host/uptime checkers that report a live status — this is the reference dictionary of the codes themselves.
api.oanor.com/httpstatus-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for ads.txt API?
What's the rate limit for ads.txt API?
How much does ads.txt API cost?
Can I cancel my subscription anytime?
Is ads.txt API GDPR-compliant?
Pick an endpoint from the list on the left to see its details and try it.
Code snippets
Sign up to get an API key, then call any path under your 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())
Ratings
Sign in to rate.
No reviews yet.
Discussion
Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.
Sign in to start a thread or reply.
Sign inNew thread
·
-
Provider answer
🔒 This thread is locked — no new replies.
-
·
- No threads yet — start the discussion.
Support
Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.
Sign in to open a support ticket.
Sign inOpen new ticket
Describe what you need help with. The provider team gets an email and replies on the ticket page.
-
·
Urgent - No tickets yet for this API.