prompt

API Versioning Architect

Design API versioning strategies that balance backward compatibility with evolution.

Updated June 2026
The prompt
Design API versioning strategy for:

API: {{api_name}}
Current version: {{current_version}}
Breaking changes needed: {{breaking_changes}}
Client diversity: {{client_types}}
Deprecation tolerance: {{deprecation_window}}

Provide:
1. Versioning scheme (URL path, header, query param, domain)
2. Backward compatibility policy (support timeline)
3. Breaking change communication plan
4. Migration path for clients (examples)
5. Feature flag usage (gradual rollout)
6. SDK/client library versioning
7. Documentation versioning strategy
8. API gateway/proxy configuration
9. Monitoring version adoption metrics
10. Sunset/deprecation timeline

Ensure {{client_types}} compatibility.
Did it work? Rate this prompt

Variables

API name or endpoint
Current version number
Planned breaking changes
Types of clients (web, mobile, partners, internal)
Deprecation period (3 months, 1 year, etc.)

Details

Author

AI Khazna

License

Security

Type

prompt

Related assets

More curated picks in Development & Code.

Audit before you install

Run any source through our checks - AI visibility, security, performance, and stack detection.

More in Development & Code