{
"url": "https://hnrss.org/frontpage",
"finalUrl": "https://hnrss.org/frontpage",
"statusCode": 200,
"contentType": "application/xml",
"discoveredFrom": null,
"cached": false,
"checkedAt": "2026-10-19T19:28:12.602Z",
"note": "Only the feed document is read. Feed items' linked pages, enclosure files and images are not requested. Feeds generated by JavaScript are not seen.",
"found": true,
"format": "rss2.0",
"feed": {
"title": "Hacker News: Front Page",
"link": "https://news.ycombinator.com/",
"description": "Hacker News RSS",
"language": null,
"updated": "Mon, 19 Oct 2026 19:14:55 +0000",
"itemCount": 20
},
"grade": "A+",
"score": 98,
"summary": {
"errors": 0,
"warnings": 0,
"infos": 2
},
"issues": [
{
"severity": "info",
"code": "xml_declaration_missing",
"message": "No <?xml version=\"1.0\" encoding=\"UTF-8\"?> declaration."
},
{
"severity": "info",
"code": "language_missing",
"message": "The channel has no <language>."
}
]
}
curl --location --request GET 'https://zylalabs.com/api/14324/rss+atom+feed+validator+api/35909/validate+rss+atom+feed+at+a+url?url=https://hnrss.org/frontpage' --header 'Authorization: Bearer YOUR_API_KEY'
{
"found": true,
"format": "rss2.0",
"feed": {
"title": "Example",
"link": "https://example.com",
"description": "Example feed",
"language": null,
"updated": null,
"itemCount": 1
},
"grade": "A",
"score": 96,
"summary": {
"errors": 0,
"warnings": 0,
"infos": 4
},
"issues": [
{
"severity": "info",
"code": "last_build_date_missing",
"message": "The channel has no <lastBuildDate>; readers use it to skip unchanged feeds."
},
{
"severity": "info",
"code": "language_missing",
"message": "The channel has no <language>."
},
{
"severity": "info",
"code": "atom_self_link_missing",
"message": "No <atom:link rel=\"self\"> in the channel; recommended so readers know the feed's own address."
},
{
"severity": "info",
"code": "item_pubdate_missing",
"message": "No item has a <pubDate>; readers cannot sort or date the items."
}
],
"checkedAt": "2026-10-19T19:28:14.628Z"
}
curl --location --request POST 'https://zylalabs.com/api/14324/rss+atom+feed+validator+api/35910/validate+feed+text+you+send+in' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{"feed":"Example https://example.comExample feed Hello https://example.com/hellohttps://example.com/hello "}'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the RSS Atom Feed Validator API simply include your bearer token in the Authorization header.
| Header | Description |
|---|---|
Authorization
|
Required
Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.
|
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
One GET, one graded JSON report: a headless RSS/Atom/JSON Feed validator for CI checks, publishing pipelines and feed directories. Give it a feed URL (or a website that links to its feed) and get a
A graded JSON report for a feed: the detected format, XML well-formedness checks, required and recommended element checks, a grade from A plus to F, a score and coded issues you can gate a CI build on.
Yes. Send the feed text in the validate endpoint and it is checked offline without any outbound request. The maximum size is 1 MB.
RSS 2.0, Atom and JSON Feed. The report states the detected format and checks the elements each format requires or recommends.
Gate on the errors count in the summary. One error alone lowers the score to 75, so the letter grade alone is not a reliable pass or fail signal.
Yes. Results for a feed URL are cached for a short time. Add the fresh parameter set to 1 to bypass the cache.
The GET endpoint returns a graded JSON report including the feed's detected format, well-formedness checks, required and recommended elements, a grade, a score, and any coded issues. The POST endpoint returns similar data but validates the feed text provided directly, without making outbound requests.
Key fields include `url`, `finalUrl`, `statusCode`, `contentType`, `found`, `format`, `grade`, `score`, and `issues`. The `feed` object contains details like `title`, `link`, `description`, and `itemCount`.
The response is structured as a JSON object with top-level fields for metadata (like `url` and `statusCode`) and a `feed` object containing specific feed details. The `issues` array lists any problems found during validation, categorized by severity.
The GET endpoint provides information about the feed's format, well-formedness, and issues found. The POST endpoint offers similar insights but focuses on the feed text submitted, allowing for offline validation without external requests.
The GET endpoint requires a `feed URL` or a webpage URL that links to a feed. The POST endpoint accepts the feed text as XML or JSON in the `feed` field, with a maximum size of 1 MB.
Users can analyze the `grade` and `score` to assess feed quality, while the `issues` array provides actionable insights for improvements. The `summary` section helps prioritize fixes based on error counts.
Typical use cases include CI checks for feed validation, ensuring feeds meet standards before publishing, and integrating feed validation into publishing pipelines to maintain content quality.
Data accuracy is maintained through structured validation checks against the required and recommended elements for each feed format. The API provides detailed feedback on any issues, allowing users to correct errors effectively.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund