URL Path Versioning
An alternate, but common, method of API versioning is to use a URL path segment. This approach does not allow implicitly
matching the initial, default API version of a service; therefore, all API versions must be explicitly declared. In
addition, the API version value specified for the URL segment must still conform to the version format. The v prefix
is not part of the API version, but may be included in route templates if you so desire.
Important
It is not possible to have a default API version for a URL path segment. This means that setting
ApiVersioningOptions.AssumedDefaultVersionWhenUnspecifiedis unlikely to have any affect when you use this method of versioning. For more information and possible solutions to address this scenario, refer to the known limitations.
Minimal API
var builder = WebApplication.CreateBuilder( args );
builder.Services.AddProblemDetails();
builder.Services.AddApiVersioning();
var app = builder.Build();
var people = app.NewVersionedApi();
var v1 = people.MapGroup( "/people/v{version:apiVersion}" ).HasApiVersion( 1.0 );
v1.MapGet( "/", () => new[] { new Person() } );
app.Run();
MVC (Core)
[ApiVersion( 1.0 )]
[ApiController]
[Route( "api/v{version:apiVersion}/[controller]" )]
public class HelloWorldController : ControllerBase
{
[HttpGet]
public string Get() => "Hello world!";
}
[ApiVersion( 2.0 )]
[ApiVersion( 3.0 )]
[ApiController]
[Route( "api/v{version:apiVersion}/helloworld" )]
public class HelloWorld2Controller : ControllerBase
{
[HttpGet]
public string Get() => "Hello world v2!";
[HttpGet, MapToApiVersion( 3.0 )]
public string GetV3() => "Hello world v3!";
}
OData
[ApiVersion( 1.0 )]
public class PeopleController : ODataController
{
[EnableQuery]
public IQueryable<Person> Get() => new[]{ new Person() }.AsQueryable();
}
[ApiVersion( 2.0 )]
[ApiVersion( 3.0 )]
[ControllerName( "People" )]
public class People2Controller : ODataController
{
[EnableQuery]
[ODataRoute]
public IQueryable<Person> Get() => new[]{ new Person() }.AsQueryable();
[EnableQuery]
[ODataRoute, MapToApiVersion( 3.0 )]
public IQueryable<Person> GetV3() => new[]{ new Person() }.AsQueryable();
}
var builder = WebApplication.CreateBuilder( args );
builder.Services.AddControllers().AddOData();
builder.Services.AddProblemDetails();
builder.Services.AddApiVersioning().AddOData(
options =>
{
options.ModelBuilder.DefaultModelConfiguration = ( builder, apiVersion, routePrefix ) =>
{
builder.EntitySet<Person>( "People" );
};
options.AddRouteComponents( "api/v{version:apiVersion}" );
} );
var app = builder.Build();
app.MapControllers();
app.Run();
The effect of the API version attribution is that the following requests match different controller implementations:
| Request URL | Matched Controller | Matched Action |
|---|---|---|
| /api/v1/helloworld | HelloWorldController | Get |
| /api/v2/helloworld | HelloWorld2Controller | Get |
| /api/v3/helloworld | HelloWorld2Controller | GetV3 |
| /api/v1/People | PeopleController | Get |
| /api/v2/People | People2Controller | Get |
| /api/v3/People | People2Controller | GetV3 |