Automated API Changelogs That Catch Breaking Changes

Theneo diffs every published spec against the last one, flags breaking changes and deprecations, writes the release notes with AI, and emails your API consumers automatically.

Automated API and Documentation Tracking

Theneo detects every change in your API — endpoint additions, parameter modifications, and breaking updates — along with any documentation edits, such as new sections or revised content. Your changelog stays accurate without anyone updating it by hand.

AI-Powered Release Summaries

Our AI analyzes all detected changes in your API and documentation to produce concise and informative release notes. This makes it easier for your users to understand the latest updates and enhancements.

Real-Time Update Subscriptions

Enable users to stay current with instant changelog notifications. Theneo lets your users subscribe to your API docs, delivering timely updates directly to their inboxes or preferred channels. This enhances user engagement and ensures they are always informed about the latest changes.

Frequently Asked Questions

Everything you need to know about Changelog.

Yes. Every time you import a new API spec and click Publish, Theneo diffs it against the previous version and logs what changed — no manual writing and no separate diff tool. Detection runs through two routes:

CI/CD pipeline integration. Connect Theneo to your existing pipeline and it identifies changes on every deploy, so anything shipped during development and release is captured automatically.

Web editor deployments. Changes made by hand in Theneo's editor are detected when you publish, so programmatic and manual updates are both covered. Everything lands on a dedicated changelog page with timestamps, giving you a full version history without anyone maintaining it.

Theneo applies widely accepted criteria rather than guessing. It currently flags:

• Optional fields becoming required
• Removed endpoints
• Modified parameter types
• Changed response structures

Each detected breaking change is labelled as such in the changelog and in the release note, so consumers can tell at a glance whether an update needs action from them.

They come from the same publish event, so they cannot drift apart. When you publish, Theneo diffs the spec, records the changes, and writes the release note from those same changes. There is no second system to update and no separate release-notes tool to keep aligned — the changelog is generated from the documentation itself. Theneo also tracks documentation edits alongside spec changes, so new sections and revised content appear in the same history as endpoint changes.

Click Ask AI and Theneo acts as your technical writer: it reads every change in the newly published spec and produces a polished release note covering new endpoints, updated descriptions, removed sections, and breaking changes.

To add one:

1. Open the Public Changelog section on your project dashboard.
2. Click Add Release Note
3. Write a short summary yourself, or click Ask AI to generate one

Yes, at field level, and without deleting anything. Open the Public Changelog tab, click Manage Visibility, and select the fields you want hidden. Hidden fields disappear from the public page while the underlying record stays fully intact, and they can be restored at any time with no data loss. Changes take effect immediately on the live page — no republishing required.

Yes. The changelog is entirely optional. Disable it any time in Project Settings → Features by toggling the changelog feature off. Individual entries can also be removed from the public changelog through your project configuration, under Public Changelog.

No. Theneo's changelog features are completely free. Your users can subscribe and receive as many updates as they want at no cost, so keeping your API consumers informed is never something you have to budget for.