Feed Parser
RSS / Atom · Developer Tools · 1 endpoint
Any RSS or Atom feed URL, parsed to normalized JSON — the plumbing under every feed reader and digest bot.
Base URL
Endpoint
Snippet
Request — cURL
v1
curl https://api.diraz.ae/v1/utility/feed \
-H "Authorization: Bearer drz_live_…"Query parameters
- feed_urlstring · required
- The feed's URL.
- max_ageinteger (seconds) · optional
- Ask for data no older than this. Clamped to the product's own floor, so it can narrow the window but never force a refresh on every call.Default: 300
Example response
200 OK
v1
{
"data": {
"feedUrl": "https://hnrss.org/frontpage",
"title": "Hacker News: Front Page",
"format": "rss",
"items": [
{
"title": "Show HN: A thing people like",
"url": "https://example.com/thing",
"publishedAt": "2026-08-22T03:14:00.000Z",
"summary": "377 points, 128 comments"
}
]
},
"meta": { "request_id": "req_7Q2fK4mZ", "as_of": "2026-08-22T04:05:00.000Z", "age_seconds": 42, "next_update_at": "2026-08-22T04:20:00.000Z" }
}- title / format
- The feed's own name, and whether it's `rss` or `atom`.
- items[].title / url / publishedAt / summary
- Every entry, one shape regardless of the feed's format.
Errors
401 Unauthorized
v1
{
"error": {
"code": "UNAUTHORIZED",
"message": "The API key is invalid, expired, or revoked."
},
"meta": {
"request_id": "req_7Q2fK4mZ"
}
}Every failure carries a stable machine-readable code before the human message, and the same meta.request_id the successful responses carry. Quote it and we can find your exact request.
Errors are free
Nothing on this page is billed. You are charged for a 2xx and nothing else — a rejected key, a bad parameter, a rate limit, or an outage on our side all cost you zero. Retry without watching the meter.
- UNAUTHORIZEDHTTP 401
- Missing, malformed, expired, or revoked API key.
- FORBIDDENHTTP 403
- The key is valid but lacks the scope this product needs.
- VALIDATION_ERRORHTTP 422
- A query parameter is the wrong type or out of range.
- RATE_LIMITEDHTTP 429
- Rate limit exhausted. `Retry-After` says how long to wait.
- SERVICE_UNAVAILABLEHTTP 503
- No data recent enough to serve. Carries `Retry-After`, and is never billed.
- Status
- Operational
- Category
- Developer Tools
- Scope
- market:read
- Rate limit
- 60 requests / 60s per key
- Pricing
- 1 credit / request
- Feed Parser
1/1 passing
Every response is timestamped. as_of is when the data was published, age_seconds how old that is now, and next_update_at when newer data is expected.
Three shapes to handle:
- Up to date200
The data is inside its published window. The overwhelming majority of requests.
- Delayeddelayed: true
Newer data is late. You still get the most recent there is, flagged so you can decide whether to use it.
- Unavailable503
Nothing recent enough to serve. Carries Retry-After, and is never billed.