Other 2xx codes
All HTTP status codes in ASP.NET Core
2xx Success
207 Multi-Status
A WebDAV response (RFC 4918) whose XML body contains a separate status for each of several resources.
In ASP.NET Core: Some APIs reuse it for batch operations; a plain 200 with per-item results is simpler for clients.
207 in .NET
The StatusCodes constant, HttpStatusCode enum name, reason phrase, class, and how EnsureSuccessStatusCode() and the standard resilience handler treat 207.
| Constant | StatusCodes.Status207MultiStatus |
|---|---|
| HttpStatusCode | HttpStatusCode.MultiStatus |
| Reason phrase | Kestrel sends Multi-Status |
| Class | 2xx, success |
| IsSuccessStatusCode | true |
| EnsureSuccessStatusCode() | does not throw |
| Standard resilience handler | does not retry it |
Returning 207
Minimal APIs
Results.StatusCode(StatusCodes.Status207MultiStatus)
Results.Problem(statusCode: StatusCodes.Status207MultiStatus, detail: "...")Controllers
StatusCode(StatusCodes.Status207MultiStatus)
Problem(statusCode: StatusCodes.Status207MultiStatus, detail: "...")The ProblemDetails body
What Results.Problem(statusCode: 207) sends (with AddProblemDetails()), as application/problem+json:
{
"title": "Multi-Status",
"status": 207,
"traceId": "0HNA1B2C3D4E5:00000001"
}A controller's Problem(statusCode: 207) sends a different body, because MVC only fills type and title for codes in ApiBehaviorOptions.ClientErrorMapping:
{
"status": 207,
"traceId": "0HNA1B2C3D4E5:00000001"
}Every response on this page was recorded from ASP.NET Core 10.0.12 on Kestrel in the Production environment; the HttpClient rows come from .NET 10.0.12 and Microsoft.Extensions.Http.Resilience 10.10.0.