LaunchNotes API

Name: LaunchNotes API
Brand: LaunchNotes API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingContent ManagementapiKey3 EndpointsREST

For Agents

Fetch published LaunchNotes announcements, read unread counts for end users, and record announcement opens so an agent can drive an in-app changelog or release-notes feed.

Install Jentic One Beta

Connect the LaunchNotes API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the LaunchNotes 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 LaunchNotes API.

Fetch the list of published announcements for embedding in an in-app what's-new feed

Retrieve the unread announcement count for a specific end user to drive notification badges

Record an announcement open event so engagement and view-through can be tracked per recipient

GET STARTED

Start building with LaunchNotes API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for LaunchNotes API, keeping it validated and agent-ready. The LaunchNotes API exposes embedded announcement feeds so product teams can surface release notes, changelogs, and feature updates inside their own apps. It returns lists of published announcements, the unread count for a given user, and accepts open-tracking events so engagement on each announcement can be measured. The surface is small and read-focused, intended for in-app what's-new widgets rather than full content authoring.

Use Cases

Patterns agents use LaunchNotes API for, with concrete tasks.

★ In-App What's-New Widget

Drive an embedded changelog or what's-new badge inside a SaaS product. The agent calls the announcement-list endpoint to render published release notes and the unread-count endpoint to display a notification badge, then posts open events back to LaunchNotes so per-user engagement is captured. Setup is a single API token and three calls.

Fetch the latest 10 announcements from /embed/announcement_list, render them in a panel, and POST a track_open event when the user clicks an entry.

Release-Note Distribution to Slack or Email

Repurpose published LaunchNotes content for outbound channels. An agent polls the announcement list on a schedule, formats each new entry as a Slack block or email summary, and forwards it to the team. Removes the need to copy release notes manually between systems and keeps internal channels in sync with the public changelog.

Poll /embed/announcement_list every 6 hours, diff against the last seen ID, and post any new entries to a Slack webhook with title and body.

Unread Indicator for Logged-In Users

Show an unread announcement count on a user avatar or notification icon. The agent calls the unread-count endpoint with the authenticated user's identifier on page load and refreshes after each open event so the badge clears in real time. Requires only the embed token and the user identifier.

Call /embed/unread for the current user on page load and decrement the displayed count after each track_open POST.

AI Agent Release-Note Briefing

An AI agent uses Jentic to discover the LaunchNotes operations and assembles a personalised briefing: it pulls the latest announcements, filters them by tag or audience, and summarises them for a user. Tracking the open back to LaunchNotes lets the product team see which agent-delivered briefings are actually being read.

Through Jentic, search 'fetch launchnotes announcements', load the schema, call the list endpoint, summarise the top 3 items, and post a track_open when the user reads the summary.

Key Endpoints

3 endpoints — jentic publishes the only available openapi specification for launchnotes api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/embed/announcement_list

Fetch published announcements for embedding

GET

/embed/unread

Get unread announcement count for a user

POST

/embed/announcements/track_open

Record an announcement open event

GET

/embed/announcement_list

Fetch published announcements for embedding

GET

/embed/unread

Get unread announcement count for a user

POST

/embed/announcements/track_open

Record an announcement open event

Why Jentic?

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

Credential isolation

The LaunchNotes API token is stored encrypted in the Jentic vault. Agents receive scoped execution capability and never see the raw token value, so embed tokens cannot leak into prompts or logs.

Intent-based discovery

Agents search Jentic with intents like 'fetch launchnotes announcements' or 'track announcement open' and Jentic returns the matching LaunchNotes operation with its input schema, so the agent can call the right endpoint without reading the developer site.

Time to first call

Direct LaunchNotes integration: a few hours to wire up the three embed endpoints, handle the token, and map responses. Through Jentic: minutes — search, load schema, execute.

FAQs

Specific to using LaunchNotes API through Jentic.

Why is there no official OpenAPI spec for LaunchNotes API?

LaunchNotes does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call LaunchNotes API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the LaunchNotes API use?

The LaunchNotes embed API uses an API key passed as a `token` query parameter on each request. Through Jentic, the token is stored encrypted in the credential vault and injected at execution time, so the raw token never enters the agent's context.

Can I track per-user announcement opens with the LaunchNotes API?

Yes. POST to /embed/announcements/track_open with the announcement identifier and a user identifier to record the open. Combine that with /embed/unread to drive an unread badge that decrements as the user reads each entry.

What are the rate limits for the LaunchNotes API?

Rate limits are not declared in the spec. The embed endpoints are designed for in-app polling, so keep refresh intervals to a few minutes or longer and cache the announcement list client-side to avoid unnecessary calls.

How do I fetch the latest announcements through Jentic?

Run `pip install jentic`, then through the Jentic SDK search for 'fetch launchnotes announcements', load the schema for GET /embed/announcement_list, and execute it with your project token. The response is the announcement feed ready to render.

Is the LaunchNotes API free?

The embed API is bundled with LaunchNotes paid plans rather than sold separately. Check launchnotes.com pricing for the plan tier that includes embedded announcement access for your project.