TEGNA · Rate Limits

Tegna Rate Limits

TEGNA publishes no rate limits for any API surface, and returns no rate-limit signal at runtime. This is a measured zero, not an unchecked gap: response headers were captured from live 200, 400, 401 and 404 responses on both publicly callable hosts and none carried a limit, a remaining count, a reset time or a Retry-After.

Tegna Rate Limits is the machine-readable rate-limit profile for TEGNA on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 2 rate-limit definitions, measuring unknown and records per page.

The profile also includes 3 backoff/retry policies defined.

Tagged areas include Broadcasting, Media, Digital Advertising, OTT, and Content API.

2 Limits
BroadcastingMediaDigital AdvertisingOTTContent APIRate Limiting

Limits

Undocumented edge protection unknown
unknown
not published
Cloudflare fronts both www.tegna.com and premion.com, and WP Engine sits behind it, so edge throttling almost certainly exists. Nothing is advertised to a client, so an integrator cannot distinguish a throttle from an outage, and cannot back off correctly.
Hard parameter ceiling (not a rate limit, but the only published bound) per-request
records per page
100
per_page is capped at 100 by the route index and enforced with a 400 rest_invalid_param / rest_out_of_bounds. Values above the cap are rejected rather than clamped. This is the only quantitative bound TEGNA's API actually publishes, and it bounds page size, not call rate.

Policies

No published throttling policy
TEGNA documents no per-second, per-minute, per-key or per-account limit for any surface, and operates no developer portal where one could be published.
Partner platform governance (advertising surface)
Programmatic and audience-data integrations for AudienceOne and Premion are transacted through third-party DSP/SSP/DMP platforms. Any throttling there is set by the partner platform, not published by TEGNA.
Crawler policy is stricter than API policy
robots.txt on both www.tegna.com and premion.com disallows GPTBot and ChatGPT-User entirely and sets Crawl-delay 10 for everyone else. The JSON APIs themselves apply no user-agent restriction — every probe in this pass succeeded with a browser user agent.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/tegna-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.