Prompt
Do I need to support old API versions in the docs?
Latest observation
Oct 10, 2026
OpenAI APIWeb search: off
Usually, yes — if those versions are still supported.
A good rule of thumb:
- Document the current version prominently
- Keep old versions documented only as long as they’re still in use or supported
- Remove or archive docs for deprecated/unsupported versions so they don’t confuse users
When you should keep old API versions in the docs
- Customers still use them
- You offer long-term support
- There are breaking changes between versions
- You need migration guidance from old to new
When you can drop them
- The version is fully deprecated
- It’s no longer supported by your backend
- You’ve given users enough notice and migration help
- You can redirect users to the new version or changelog
Best practice
Instead of mixing everything together, use:
- Versioned docs (
/v1,/v2) - A “latest” docs entry point
- A migration/changelog page
- Clear labels like Supported, Deprecated, End of life
If you want, I can help you design a simple docs/versioning policy for your API.