207 Multi-Status (RFC 4918, WebDAV) is used when one request involves several resources or properties, for example PROPFIND or PROPPATCH, or a COPY, MOVE or DELETE on a collection. The body is an XML multistatus document in which each response element names a resource (href) and gives its own status, such as 200 OK, 403 Forbidden or 423 Locked.
The 207 itself only means that the request was processed; the client has to read the body to learn what actually succeeded. Some JSON APIs have borrowed 207 for batch endpoints that report a result per item.
WebDAV clients include file managers such as Windows Explorer and macOS Finder, office applications and the sync clients of file-hosting services.
Example response
HTTP/1.1 207 Multi-Status
Date: Fri, 06 Nov 2026 10:15:32 GMT
Content-Type: application/xml; charset=utf-8
Content-Length: 309
<?xml version="1.0" encoding="utf-8"?>
<d:multistatus xmlns:d="DAV:">
<d:response>
<d:href>/docs/report.pdf</d:href>
<d:status>HTTP/1.1 200 OK</d:status>
</d:response>
<d:response>
<d:href>/docs/plan.docx</d:href>
<d:status>HTTP/1.1 423 Locked</d:status>
</d:response>
</d:multistatus>SEO and redirect checking
WebDAV traffic is not crawled, so 207 has no SEO effect. A public page should never answer an ordinary GET with 207; if a redirect check shows it, the URL points to a WebDAV or batch API endpoint.
Common causes and use cases
PROPFINDlists a folder and returns properties for every file in it.DELETEorMOVEof a folder partly fails because one file is locked.- A batch API reports a separate result for each item in the request.