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
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 →DPI Calculator — Print Resolution Tool
Calculate DPI (dots per inch), image dimensions, and print sizes. Convert between pixels and physical dimensions for printing and displays.
Use Tool →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 →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 →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 →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 →Seconds to Time Converter — HH:MM:SS Formatter
Convert seconds to HH:MM:SS time format instantly with precise calculations and easy-to-read formatting.
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 →Related API & Backend Tools
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 →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 →API Mock Server Config Generator — Build Instant Mock Endpoints Online
Paste API route definitions to instantly generate JSON configuration files for json-server, Mockoon, and Prism mock servers. Define routes as METHOD /path lines and get ready-to-use config with realistic sample data.
Use Tool →Postman to OpenAPI Converter — Spec Migration Tool
Convert Postman Collection v2.1 JSON to OpenAPI 3.0 specification format. Upload or paste your collection, and get a downloadable openapi.yaml or openapi.json with mapped paths, parameters, request bodies, and example responses.
Use Tool →GraphQL Subscription Builder — Generate WebSocket Payloads and Client Queries
Build GraphQL subscription query strings and generate WebSocket connection code snippets for Apollo Client, urql, and graphql-ws. Define your operation name, variables, and selection fields visually, then copy the ready-to-use code.
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 →API Error Decoder — Fix Suggestion Tool
Decode HTTP status codes and OAuth 2.0 error strings with plain-English descriptions, common causes, and actionable fix suggestions. Covers every HTTP 1xx–5xx status code and all standard OAuth 2.0 error responses. Results appear instantly as you type.
Use Tool →GraphQL Cost Estimator — Analyze Query Complexity and Depth
Assign custom field weights to a GraphQL schema and calculate the total query complexity score. Paste any GraphQL query, configure per-field costs, and get a per-field breakdown table showing depth, multipliers, and cumulative cost.
Use Tool →Share Your Feedback
Help us improve this tool by sharing your experience