API Changelog Generator helps developers auto-generate standardized Changelog documents from API endpoint changes. Supports semantic versioning suggestions, multiple output formats, and change categorization.
• Six change types: Added/Changed/Deprecated/Removed/Fixed/Security
• Semantic versioning: Auto-suggest version numbers by change type
• Multiple output formats: Markdown/JSON/HTML
• Batch import: JSON format bulk change import
• Keep a Changelog convention: Community standard compliance
1. Fill in version number and date
2. Add change entries (select type + description)
3. Or batch import via JSON
4. Select output format and generate
5. Copy or download the Changelog
• API Releases: Auto-generate change records for each release
• Team Collaboration: Standardize change record format
• Documentation: Auto-maintain CHANGELOG.md
• CI/CD Integration: Export JSON for automation pipelines
Keep a Changelog is a community-maintained convention suggesting Added/Changed/Deprecated/Removed/Fixed/Security categories. Semantic Versioning (SemVer) uses MAJOR.MINOR.PATCH: breaking changes bump MAJOR, new features bump MINOR, fixes bump PATCH. A good Changelog is key to API maintainability.
An API changelog records every change to an API, including new endpoints, modified parameters, removed features. It helps consumers understand changes and assess upgrade impact.
Supports Added, Changed, Deprecated, Removed, Fixed, and Security — six standard types following Keep a Changelog convention.
Based on SemVer: new features → MINOR, breaking changes → MAJOR, fixes → PATCH. The tool auto-suggests version numbers.
Default Markdown following Keep a Changelog. Also supports JSON for automation integration.
Yes. Custom title format, date format, category order, and custom change types.
Yes. Batch import via JSON format, or add individually with type and description.