Do I need a public docs site for every API release?

Not necessarily.

A public docs site for every API release is useful if your users need to discover, understand, and adopt each version independently. But in many cases, one well-maintained docs site with versioning is enough.

Good reasons to have a public docs site per release

• You make breaking changes between versions.
• Old versions must stay usable for existing customers.
• You want each release to have its own examples, changelog, and reference.
• Your API is public-facing and versioned by URL or header.

When you probably don’t need separate sites

• Changes are mostly backward-compatible.
• You can support versioned docs within one site.
• Your audience is internal or tightly managed.
• You use one canonical docs site plus release notes and an API changelog.

Common best practice

Maintain:

• One main docs portal
• Version selector for stable releases
• Release notes / changelog
• Deprecation notices
• Optional archived docs for older major versions

This gives users access to older docs without multiplying your maintenance burden.

Rule of thumb

If a release changes the API in a way that would confuse or break existing integrations, document it clearly and keep that version accessible.
If it’s just a minor update, a public release note on the same docs site is usually enough.

If you want, I can also suggest a docs/versioning strategy based on whether your API is public, internal, or partner-facing.