How the Releasebot JSON Endpoint Works

The Releasebot JSON endpoint allows Releasebot Pro users to access their feed in JSON format.

It's a simple way to programmatically access your feed without worrying about API keys or credits.

Here are some things to know about it:

What the endpoint returns

The JSON endpoint returns the 20 most recent releases 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 one field:

• releases — an array of up to 20 release objects

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-5a1362040b3f.json

Need pagination or more control?

If you need to page through older releases or filter by date, the Releasebot API v1 has a /api/v1/feed endpoint that supports pagination, a configurable limit, and a since parameter. It uses your API key instead of your user ID.

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].