API Changelog Generator — Automatically Detect Breaking Changes and Write Release Notes
Convert API change descriptions into structured Keep-a-Changelog format. Enter a version, date, and one change per line prefixed with its type (added, changed, deprecated, removed, fixed, or security). The tool instantly groups them into the canonical section order and outputs a ready-to-paste CHANGELOG.md block. Supports four real-world presets for REST API releases, breaking changes, patch releases, and unreleased work. Free and runs entirely in your browser.
How to Use API Changelog Generator — Automatically Detect Breaking Changes and Write Release Notes
How to Use the API Changelog Entry Generator:
Load a Preset (Optional): Click any preset at the top to pre-fill all fields with a realistic example. REST API release shows a minor version with new endpoints. Breaking change demonstrates a major version with removed routes. Patch release covers bug fixes and security patches. Unreleased shows how to maintain an [Unreleased] section at the top of your CHANGELOG.md. Each preset is fully editable after loading.
Enter a Version Number: Type a semantic version number such as 2.4.0 in the Version field. For work that has not yet shipped, type Unreleased — this follows the Keep-a-Changelog convention of maintaining an [Unreleased] section that accumulates changes until the next release.
Set the Release Date: The Date field is pre-filled with today's date in ISO 8601 format (YYYY-MM-DD) as required by the Keep-a-Changelog specification. Update it to the planned or actual release date. Leave the field clear to omit the date from the heading.
Add a Compare URL (Optional): Paste a GitHub, GitLab, or Bitbucket comparison URL between the previous version and the current version. For example: https://github.com/org/repo/compare/v2.3.0...v2.4.0. When provided, the version heading becomes a link in the output — a Keep-a-Changelog best practice that lets readers browse the exact diff for every release.
Enter Change Entries: In the Change Entries textarea, add one entry per line. Each line should start with a type prefix followed by a colon and the change description. The supported prefixes are: added (or feat, new), changed (or update, modify), deprecated, removed (or delete, breaking), fixed (or fix, bug, bugfix, hotfix, patch), and security (or sec, cve, vuln). You can also use bracket notation such as [added] or [fixed]. Lines without a recognised prefix are grouped under Changed by default.
Read the Output: The right panel shows the formatted CHANGELOG.md block in real time. Changes are automatically grouped into the canonical section order defined by Keep-a-Changelog: Added, Changed, Deprecated, Removed, Fixed, Security. Each section only appears if it has at least one entry.
Check Warnings: If a line uses an unrecognised type prefix, a warning appears above the output identifying the line number and fallback type used. This lets you spot and correct typos without losing any entries.
Copy or Download: Click Copy to copy the formatted block to the clipboard and paste it directly into your CHANGELOG.md. Click .md to download a standalone CHANGELOG.md file containing only the generated block, useful for code review attachments or release documentation.
Common Use Cases:
- API release documentation: Format all changes for an API release into the standard Keep-a-Changelog structure before pushing to your repository.
- PR description generation: Generate a structured change summary for the pull request body or GitHub Release notes.
- Onboarding developers: Use presets to teach new team members the correct format for changelog entries before they start contributing.
- Backfilling changelogs: Quickly format historical release notes collected from commit messages or Jira tickets into consistent changelog entries.
- Breaking change communication: Use the Breaking change preset as a template when planning a major version with endpoint removals.
Tips and Best Practices:
- Follow semantic versioning (semver.org): increment the patch version for fixes, minor for backwards-compatible additions, and major for breaking changes.
- Use Unreleased as the version string while a release is in progress — replace it with the version number and date on the day you ship.
- Keep each entry to a single, concise sentence. Describe the change from the API consumer's perspective, not the implementation detail.
- Use the deprecated section to give consumers advance notice before removing an endpoint. Always pair a deprecated entry with a migration path in the description.
- Avoid words like "various", "several", or "misc" in entries — each change should be specific enough that a consumer can act on it.
Frequently Asked Questions
Most Viewed Tools
TOTP Code Generator — 2FA Testing Tool
Generate time-based one-time passwords from a TOTP secret key. Enter your base32 secret, choose a period and digit length, and get the current and next codes with a live countdown timer. Useful for testing and debugging 2FA integrations.
Use Tool →JSON to Zod — Schema Generator
Generate Zod validation schema code from a JSON sample object. Infers z.string(), z.number(), z.boolean(), z.array(), z.object(), and z.null() types automatically. Handles nested objects, arrays of objects with optional field detection, and outputs copy-ready TypeScript with import and z.infer type alias.
Use Tool →JSONL Formatter — Line-by-Line Validator
Format, validate, and inspect JSON Lines (JSONL) and NDJSON files. Validates each line individually, reports parse errors by line number, outputs compact JSONL or a pretty-print preview, and lets you download the cleaned file.
Use Tool →Screen Size Converter — Diagonal Dimension Tool
Calculate screen width and height from diagonal size and aspect ratio. Convert between inches and centimeters for displays, TVs, and monitors with instant dimension calculations.
Use Tool →Password Entropy Calculator — Crack Time Estimator
Calculate the information-theoretic bit entropy of any password or API key. Detects character set pools automatically, shows the total number of possible combinations, and estimates crack time across five attack scenarios from rate-limited web logins to GPU cracking clusters.
Use Tool →TLS Cipher Suite Checker — Strength Analyzer
Check TLS protocol version compatibility and cipher suite strength ratings against current best practices. Supports IANA and OpenSSL cipher names — rates each suite as Strong, Weak, or Deprecated and explains why.
Use Tool →Secret Scanner — API Key & Credential Detector
Scan pasted text, code, or config files for accidentally exposed API keys, tokens, passwords, and private keys. Detects 50+ secret types across AWS, GitHub, Stripe, OpenAI, and more — all client-side, nothing leaves your browser.
Use Tool →TOML Config Validator — Syntax Error Finder
Validate TOML configuration file syntax and report errors with line numbers. Paste any TOML content — Cargo.toml, pyproject.toml, config.toml — and instantly see a green checkmark with key counts and structure stats, or a precise error message pointing to the exact line. Includes a collapsible JSON structure preview to confirm what was parsed.
Use Tool →Related API & Backend Tools
REST Endpoint Documenter — Markdown Doc Generator
Document a REST endpoint quickly by entering the URL, method, headers, and sample request/response. Generates formatted Markdown documentation and an example cURL command instantly.
Use Tool →GraphQL Variables Formatter — Query Validator
Format and validate GraphQL query variables JSON for use in queries and API clients. Paste your variables JSON alongside a GraphQL query to instantly format the JSON, validate that each variable matches its declared type, catch missing required variables, and highlight undeclared extras.
Use Tool →OAuth Token Validator — JWT & OIDC Decoder
Validate and inspect OAuth tokens in your browser. Decode JWT access tokens and ID tokens to view claims, scopes, and expiry. Analyse opaque tokens for entropy and format. Free and private.
Use Tool →Webhook Retry Config Calculator — Simulate Exponential Backoff & Jitter
Configure exponential backoff parameters and preview the full retry schedule for webhook delivery. Enter max attempts, initial delay, multiplier, jitter, and a max delay cap to instantly see each retry timestamp, cumulative elapsed time, jitter range, and which delays hit the cap. Supports presets for standard, aggressive, conservative, Stripe-style, and fixed-interval retry policies. Free and runs entirely in your browser.
Use Tool →API Latency Budget Calculator — Plan Distributed System Performance
Set a P99 SLO latency target and distribute the budget across your upstream service dependencies. See remaining headroom, utilization percentage, a stacked allocation bar, and a per-service breakdown with optional P99 actual measurements.
Use Tool →API Mock Data Generator — Realistic JSON Builder
Generate structured, realistic mock data for API endpoint testing. Define fields with names and types — UUID, name, email, integer, enum, date, and more — set how many rows you need, and export as a JSON array, NDJSON, or CSV. All generation runs entirely in your browser with no data sent to any server.
Use Tool →HTTP Retry Policy Builder — Configure Resilient API Client Logic
Configure max retries, initial delay, backoff multiplier, jitter, max delay cap, and retryable HTTP status codes to instantly generate ready-to-use retry policy code for Axios (with axios-retry), native Fetch API (Node 18+ and node-fetch), and Go net/http. Supports presets for Standard, Aggressive, Conservative, and Rate-Limit Aware policies. All code is generated in your browser — free, instant, no signup.
Use Tool →OpenAPI Mock Generator — Turn API Specs into Live Mock Servers
Paste an OpenAPI 3.x or Swagger 2.0 spec, select any endpoint, and instantly get a realistic mock request body and response matching the defined schemas. Also generates a ready-to-run cURL command.
Use Tool →Share Your Feedback
Help us improve this tool by sharing your experience