How the Releasebot JSON Endpoint Works

The Releasebot JSON endpoint allows Releasebot Pro users to access their feed in JSON format. Here are some things to know about it:

What the endpoint returns

The JSON endpoint returns the release notes from your personal Releasebot feed, in reverse chronological order (newest first). It's the same content you see on your dashboard, but in a format you can consume programmatically.

Each release includes the product and vendor it belongs to, the release date, a formatted content summary, and a link back to the original source.

How the endpoint is structured

The endpoint lives at:

GET https://releasebot.io/api/feed/{your-user-id}.json

You can find your full URL on the Alerts & Integrations page. The response is a JSON object with two fields:

• releases — an array of up to 20 release objects
• nextOffset — the offset to pass for the next page, or null if there are no more results

Each release object contains:

• id — the release ID
• slug — a URL-friendly identifier
• release_details — structured metadata about the release
• release_date — the date the release was published (when available)
• created_at — the date Releasebot discovered the release
• formatted_content — a summary of the release in Markdown
• product — the product name, slug, and associated vendor
• source — the original source URL

What a sample response looks like

You can view a live sample response here: https://releasebot.io/api/feed/45b93d21-f8c4-4fb9-9564-5a1362540b3f.json

How pagination works

The endpoint returns 20 releases at a time. To get the next page, pass the offset query parameter:

GET https://releasebot.io/api/feed/{your-user-id}.json?offset=20

The response includes a nextOffset field. If it's a number, there are more results — pass it as the offset for your next request. If it's null, you've reached the end.

For example, to page through your entire feed:

1. ?offset=0 (or no offset) — returns releases 1–20, nextOffset: 20
2. ?offset=20 — returns releases 21–40, nextOffset: 40
3. ?offset=40 — returns releases 41–50, nextOffset: null (done)

Rate limit

The endpoint is rate limited to one request per second. This should be more than enough for any reasonable use case. If you need to pull your full feed history, just add a one-second delay between paginated requests and you'll be fine.

That's it!

The JSON endpoint is meant to be a simple way to interact with your release note feed programmatically. If you have more advanced data needs, please reach out to us at [email protected].