Monitor Yardbarker's cross-publisher sports coverage
Use Yardbarker endpoints to turn monitor yardbarker's cross-publisher sports coverage into repeatable API requests with documented inputs and JSON responses.
Better Collective-owned sports and entertainment publisher combining in-house reporting with independent sports publishers and editorial/algorithmic curation. Refresh the typed directory before building recurring section jobs: its sport, team, school, and topic slugs are the only values accepted by /headlines. That route accepts a section only, with no page, limit, date, or feed-window input, so treat results as a recent snapshot rather than a pageable archive. Keep homepage top-story cards separate from section RSS summaries, which omit long-form content:encoded. Follow canonical returned story URLs with /article and canonical contributor-profile URLs with /author; retain the original section so syndicated and in-house voices stay attributable.
Collect a sports and entertainment publisher owned by Better Collective, combining in-house reporting with independent sports publishers.
Endpoint families
5
Documented params
8
Examples
5
Live catalog snapshot
Active endpoints
5
Methods
GET
Required params
8
Schema refs
5
{
"platform": "Yardbarker",
"endpoint": "yardbarker-sections",
"method": "GET",
"path": "/yardbarker/sections",
"auth": "apiKey"
}Use cases
Collect a sports and entertainment publisher owned by Better Collective, combining in-house reporting with independent sports publishers.
Use Yardbarker endpoints to turn monitor yardbarker's cross-publisher sports coverage into repeatable API requests with documented inputs and JSON responses.
Use Yardbarker endpoints to turn separate yardbarker feed records from article or profile follow-up into repeatable API requests with documented inputs and JSON responses.
Use Yardbarker endpoints to turn preserve source urls, dates, and access outcomes for review into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Yardbarker endpoint catalog — 5 endpoints, 8 documented request parameters, and 5 published response schemas — the same catalog Docs and Playground run against.
5 documented Yardbarker endpoints, grouped into 5 request families — Article, Author and Headlines, plus 2 more.
8 request parameters are documented across those Yardbarker endpoints, 8 of them required — the full input contract is public before you write any integration code.
5 of the 5 Yardbarker endpoints ship a recorded example response, and 5 carry a documented response schema — you can code against the real JSON before the first request.
Yardbarker endpoints document their error responses (400, 404, 429 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
5 hosted MCP tools back the Yardbarker endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
/yardbarker/article
/yardbarker/author
/yardbarker/headlines
/yardbarker/news
/yardbarker/sections
Endpoint catalog
/yardbarker/articleExtracts metadata and the publicly served text paragraphs from a canonical Yardbarker story URL. Quiz, account, player, and non-article URLs are rejected.
MCP tool yardbarker_article
/yardbarker/authorReturns a Yardbarker author profile from a canonical author `url` of the form `https://www.yardbarker.com/authors/<slug>/<id>` (required). The response has the name, profile image when provided and linked recent stories. Biography text and pagination are not available.
MCP tool yardbarker_author
/yardbarker/headlinesLists recent Yardbarker headlines with short summaries for one section. `section` is required and takes a typed slug from `yardbarker-sections`, such as `sport_1`, `team_18`, `school_506` or `topic_16979`. Items have title, URL, summary, author, time and image. Unknown slugs return a 400 error.
MCP tool yardbarker_headlines
/yardbarker/newsReturns recent Yardbarker story metadata and short summaries from its public homepage. Use /yardbarker/sections to discover the supported sports, team, school, and topic sections.
MCP tool yardbarker_news
/yardbarker/sectionsLists the 589 Yardbarker sections as a dated snapshot: 88 sports hubs, 278 team pages, 150 school pages and 73 topics. Each has a typed `slug` (such as `sport_1` or `team_18`), a display `name` and a hub `url`. Use the slug as `section` in `yardbarker-headlines`. Takes no parameters.
MCP tool yardbarker_sections
Related APIs
Media & Streaming
Follow German football from the Bundesliga down to the lowest Kreisklasse. Discover competitions in all 22 federations, then read matchdays, standings, scorers, clubs, teams, and players from the DFB's own amateur-football portal.
Media & Streaming
Browse Sportskeeda's sports and entertainment coverage, community wikis, quizzes, and fan games with the catalog's current slugs and filter limits.
Media & Streaming
Research streaming catalogs, title availability, providers, offers, seasons, episodes, and release changes from JustWatch with normalized JSON.
How to scrape Yardbarker
Yardbarker is a sports and entertainment publisher owned by Better Collective, combining in-house reporting with independent sports publishers and editorial/algorithmic curation. A live /yardbarker/sections response on 2026-10-14 contained 589 directory records; refresh it before scheduling because publisher feeds change. Refresh the typed directory before building recurring section jobs: its sport, team, school, and topic slugs are the only values accepted by /headlines. That route accepts a section only, with no page, limit, date, or feed-window input, so treat results as a recent snapshot rather than a pageable archive. Keep homepage top-story cards separate from section RSS summaries, which omit long-form content:encoded. Follow canonical returned story URLs with /article and canonical contributor-profile URLs with /author; retain the original section so syndicated and in-house voices stay attributable. The article route validates canonical Yardbarker story URLs and returns paragraphs available on the public anonymous page; it does not bypass access limits. The author route accepts a canonical profile URL, not a free-text byline search, and returns recent linked stories without biography text or pagination. Headline summaries are not full article bodies, and the directory can change over time. Use the endpoint cards for this integration's accepted inputs. Publisher reference: https://www.yardbarker.com/about/
A live /yardbarker/sections response on 2026-10-14 contained 589 directory records; refresh it before scheduling because publisher feeds change. Refresh the typed directory before building recurring section jobs: its sport, team, school, and topic slugs are the only values accepted by /headlines. That route accepts a section only, with no page, limit, date, or feed-window input, so treat results as a recent snapshot rather than a pageable archive. Keep homepage top-story cards separate from section RSS summaries, which omit long-form content:encoded. Follow canonical returned story URLs with /article and canonical contributor-profile URLs with /author; retain the original section so syndicated and in-house voices stay attributable.
Yardbarker says its editors and recommendation algorithms surface work from its newsroom and hundreds of independent sports publishers; Better Collective has owned the company since 2024. Its live-verified directory contains typed sports hubs, team pages, school pages, and topics. Discover current values first and pass only an exact returned slug to /headlines. That route accepts a section only; it has no page, limit, date, or feed-window parameter. /news is a separate homepage snapshot, while section headlines contain short RSS summaries and omit the long content:encoded body. The author route accepts a canonical profile URL—not a free-text byline search—and returns linked recent stories, not biography text or paginated history.
Yardbarker says its editors and recommendation algorithms surface work from its newsroom and hundreds of independent sports publishers; Better Collective has owned the company since 2024. Its live-verified directory contains typed sports hubs, team pages, school pages, and topics. Discover current values first and pass only an exact returned slug to /headlines. That route accepts a section only; it has no page, limit, date, or feed-window parameter. /news is a separate homepage snapshot, while section headlines contain short RSS summaries and omit the long content:encoded body. The author route accepts a canonical profile URL—not a free-text byline search—and returns linked recent stories, not biography text or paginated history. Pass only a value returned by /yardbarker/sections and accepted by /yardbarker/headlines; preserve the selected desk with its results.
The article route validates canonical Yardbarker story URLs and returns paragraphs available on the public anonymous page; it does not bypass access limits. The author route accepts a canonical profile URL, not a free-text byline search, and returns recent linked stories without biography text or pagination. Headline summaries are not full article bodies, and the directory can change over time. Keep teaser, truncation, premium, or access fields beside the canonical URL so downstream users can see what the publisher actually returned.
Refresh the typed directory before building recurring section jobs: its sport, team, school, and topic slugs are the only values accepted by /headlines. That route accepts a section only, with no page, limit, date, or feed-window input, so treat results as a recent snapshot rather than a pageable archive. Keep homepage top-story cards separate from section RSS summaries, which omit long-form content:encoded. Follow canonical returned story URLs with /article and canonical contributor-profile URLs with /author; retain the original section so syndicated and in-house voices stay attributable. The article route validates canonical Yardbarker story URLs and returns paragraphs available on the public anonymous page; it does not bypass access limits. The author route accepts a canonical profile URL, not a free-text byline search, and returns recent linked stories without biography text or pagination. Headline summaries are not full article bodies, and the directory can change over time.
FAQ
A live /yardbarker/sections response on 2026-10-14 contained 589 directory records; refresh it before scheduling because publisher feeds change. Refresh the typed directory before building recurring section jobs: its sport, team, school, and topic slugs are the only values accepted by /headlines. That route accepts a section only, with no page, limit, date, or feed-window input, so treat results as a recent snapshot rather than a pageable archive. Keep homepage top-story cards separate from section RSS summaries, which omit long-form content:encoded. Follow canonical returned story URLs with /article and canonical contributor-profile URLs with /author; retain the original section so syndicated and in-house voices stay attributable.
The article route validates canonical Yardbarker story URLs and returns paragraphs available on the public anonymous page; it does not bypass access limits. The author route accepts a canonical profile URL, not a free-text byline search, and returns recent linked stories without biography text or pagination. Headline summaries are not full article bodies, and the directory can change over time.
No. /headlines accepts one required section slug and has no page, limit, date, or feed-window parameter. Use /sections to discover current sports, team, school, or topic slugs, then treat each recent headline response as a current feed snapshot. The short RSS summaries omit content:encoded; follow a canonical story URL to /article when public article paragraphs are needed.