Recommend an API versioning strategy based on these examples. Examples: Scenario: Public API with long-lived integrations Strategy: URL path versioning (/v1/, /v2/) Rationale: Clear separation, easy to document, clients can migrate gradually Scenario: Internal microservices with frequent changes Strategy: Header versioning (Accept: application/vnd.api+json;version=2) Rationale: Clean URLs, flexible evolution, service mesh compatible Scenario: Mobile app with forced updates possible Strategy: Query parameter (?api_version=2024-01) Rationale: Date-based, simple tracking, easy analytics Your scenario: {{api_description}} Client types: {{client_types}} Change frequency: {{change_frequency}} Recommend strategy with rationale.
API Versioning Strategy Selection
Recommend API versioning strategies based on scenario examples.
11 copies0 forks
Share this prompt:
Details
Category
CodingUse Cases
API design decisionsVersioning strategy planningArchitecture guideline creation
Works Best With
claude-opus-4.5gpt-5.2gemini-2.0-flash
Created Updated Shared