What it means
A WebDAV response whose XML body contains a separate status for each of several resources affected by one request.
Common causes
- PROPFIND listing a folder
- A batch COPY, MOVE or DELETE where items had different outcomes
How to fix it
As a client or visitor
Parse every <response> element; some items may have failed even though the overall status is 207.
As the site or API owner
Use 207 only for WebDAV or clearly documented batch APIs, and report a per-item status for each resource.
Example response
HTTP/1.1
HTTP/1.1 207 Multi-Status
Date: Tue, 07 Oct 2025 09:30:00 GMT
Server: nginx
Content-Type: application/xml; charset=utf-8
<?xml version="1.0" encoding="utf-8"?>
<d:multistatus xmlns:d="DAV:">
<d:response>
<d:href>/files/report.pdf</d:href>
<d:status>HTTP/1.1 200 OK</d:status>
</d:response>
</d:multistatus>Specification
FAQ
› Is 207 success or failure?
Neither by itself. It means "see the body": each item has its own status.
› Should REST APIs use 207?
Some batch APIs do, but many prefer 200 with a per-item result array, which is easier for JSON clients.