Skip to content
verikt

api-versioning capability

api-versioning adds version routing to your Go service, letting you evolve your API without breaking existing clients.

What You Get

Section titled “What You Get”
  • Version routing
  • Header/path-based versioning strategies

When to Use

Section titled “When to Use”

Add api-versioning when you need to maintain backward compatibility while evolving your API contract. Useful for public APIs, mobile-facing backends (where clients can’t be force-upgraded), and any service with external consumers.

Requirements & Suggestions

Section titled “Requirements & Suggestions”

Requires: http-api

Add to Your Service

Section titled “Add to Your Service”
Terminal window
verikt new my-service --language go --cap http-api,api-versioning
# or add to an existing service:
verikt add api-versioning
Section titled “Related Capabilities”

http-api

The Chi router foundation required by this capability.

cors

CORS support for browser clients across API versions.

auth-jwt

JWT authentication applied consistently across versions.