Newreleasesio NewReleases API

Name: NewReleases API
Brand: NewReleases API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsMonitoring ObservabilityapiKey28 EndpointsREST

For Agents

Track software release notifications across package registries and route them to chat tools. Manage projects, releases, tags, and integrations like Slack, Discord, and Microsoft Teams.

Install Jentic One Beta

Connect the NewReleases API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the NewReleases API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with NewReleases API.

Track new releases for packages across GitHub, npm, PyPI, Docker Hub, and 70+ other providers

Retrieve full release history and release notes for any tracked project

Route release notifications to Slack, Discord, Microsoft Teams, Mattermost, Rocket.Chat, and Telegram channels

GET STARTED

Start building with NewReleases API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use NewReleases API for, with concrete tasks.

★ Dependency Update Monitoring

Engineering teams use NewReleases to receive alerts when upstream packages publish new versions across npm, PyPI, Maven, NuGet, and Docker Hub. Add projects via POST /v1/projects, list current trackers with GET /v1/projects, and read release notes through GET /v1/projects/{id}/releases/{version}/note. This replaces ad-hoc RSS or watch lists and gives a single feed for every dependency a team cares about.

Add the github/kubernetes/kubernetes project to tracking and configure a Slack channel notification when a new release is published

ChatOps Release Notifications

DevOps teams pipe release events into Slack, Microsoft Teams, Discord, Mattermost, or Rocket.Chat so engineers see new versions where they already work. List wired channels through GET /v1/slack-channels, GET /v1/discord-channels, and GET /v1/microsoft-teams-webhooks, then update per-project settings with POST /v1/projects/{id} to specify which integration receives that project's alerts.

Configure the project with id abc123 to push release notifications to a specific Slack channel and Microsoft Teams webhook

Tag-Based Release Organisation

Platform teams managing dozens or hundreds of tracked projects organise them with tags representing team ownership, criticality, or technology stack. Create tags through POST /v1/tags, list existing tags via GET /v1/tags, and apply them when adding or updating projects. This makes filtering and reporting on release velocity per team practical at scale.

Create a tag named security-critical and apply it to the openssl, log4j, and curl project trackers

Agent-Driven Release Triage

An AI agent can call NewReleases through Jentic to monitor the dependency tree of a codebase, fetch release notes when new versions appear, and summarise breaking changes for a human reviewer. The agent uses GET /v1/projects/{id}/latest-release to detect new versions and GET /v1/projects/{id}/releases/{version}/note to pull the changelog without scraping vendor sites.

For every tracked project, fetch the latest release and its release note, then summarise breaking changes for the engineering lead

Key Endpoints

28 endpoints — newreleases api tracks software release notifications across 75+ package providers including github, npm, pypi, docker hub, and maven central.

METHOD

PATH

DESCRIPTION

GET

/v1/projects

List all tracked projects

POST

/v1/projects

Add a project to tracking

GET

/v1/projects/{id}/releases

List releases for a project

GET

/v1/projects/{id}/latest-release

Get the latest release for a project

GET

/v1/projects/{id}/releases/{version}/note

Get release notes for a specific version

POST

/v1/tags

Create a tag for grouping projects

GET

/v1/slack-channels

List configured Slack notification channels

GET

/v1/projects

List all tracked projects

POST

/v1/projects

Add a project to tracking

GET

/v1/projects/{id}/releases

List releases for a project

GET

/v1/projects/{id}/latest-release

Get the latest release for a project

GET

/v1/projects/{id}/releases/{version}/note

Get release notes for a specific version

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

NewReleases API keys are stored encrypted in the Jentic vault. Agents receive a scoped credential reference, so the X-Key header is injected by Jentic at execution time — the raw key never enters the agent's context window or chat history.

Intent-based discovery

Agents search Jentic with intents like 'track a new package release' or 'send a release alert to slack' and Jentic returns the matching NewReleases operation along with its input schema, so the agent calls the right endpoint without reading the docs site.

Time to first call

Direct integration: half a day to read the docs, wire the X-Key header, handle pagination, and respect the 1-per-hour GET rate limit. Through Jentic: under 15 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

GitHub API

GitHub Releases endpoint provides release data for GitHub-hosted projects only, without cross-registry coverage

Choose GitHub when you only need to track GitHub repositories and want the full release payload directly from the source. Choose NewReleases when you need a single feed across npm, PyPI, Docker Hub, and other registries.

Complementary

Snyk API

Snyk reports security vulnerabilities in dependencies; NewReleases reports new releases of those dependencies

Use Snyk to decide whether a dependency is unsafe, and NewReleases to learn when a fixed version has shipped so the agent can open an upgrade pull request.

Complementary

Slack API

Slack receives the release notifications NewReleases routes through its Slack integration

Use the Slack API directly when an agent needs to post a custom-formatted release summary or thread replies; use NewReleases' built-in Slack integration for plain release alerts.

FAQs

Specific to using NewReleases API through Jentic.

What authentication does the NewReleases API use?

The NewReleases API uses an API key passed in the X-Key header, with HTTP Basic auth as an alternate scheme. Through Jentic the key is stored in the encrypted vault and never enters the agent's prompt context — agents call the API with a scoped Jentic credential reference instead.

Can I track releases from private GitHub repositories with the NewReleases API?

The API tracks any project that has been added through POST /v1/projects and is supported by one of the providers returned by GET /v1/providers. Public package registries and public repositories work directly; private repository support depends on your NewReleases account plan and the provider integration.

What are the rate limits for the NewReleases API?

GET requests are limited to 1 per hour and other requests to 10 per hour, enforced per API key. Every response includes X-Ratelimit-Limit, X-Ratelimit-Remaining, and X-Ratelimit-Reset headers so callers can pace their requests; agents calling through Jentic should batch project additions and tag changes rather than issuing them one at a time.

How do I send NewReleases alerts to Slack through Jentic?

Connect Slack inside the NewReleases dashboard so its workspace appears under GET /v1/slack-channels, then use POST /v1/projects/{id} to attach that channel to a project's notification settings. Through Jentic, the agent searches for 'configure slack release notification', loads the schema, and executes the call with the project id and channel id.

Is the NewReleases API free to use?

NewReleases offers a free tier suitable for individual developers and paid tiers for teams with more tracked projects and integrations. The API surface itself is the same across plans — what changes is the number of trackable projects and which chat integrations are unlocked.

Can I retrieve release notes without scraping the GitHub or npm page?

Yes. GET /v1/projects/{id}/releases/{version}/note returns the structured release note that NewReleases captured at publish time, which is what makes this API useful for AI agents that summarise changelogs across a dependency tree.