207 Multi-Status
One response carrying many: a status per resource, wrapped in XML.
WebDAV works in batches — a PROPFIND lists a whole folder, a DELETE can sweep a tree. A single code cannot cope, so RFC 4918 invented 207: the XML body carries one status for every resource touched.
Anyone syncing files with Nextcloud, calendars over CalDAV or contacts over CardDAV receives 207 all day without knowing. It is bureaucratic success: it worked, but the answer comes as a form.
HTTP/1.1 207 Multi-Status
Content-Type: application/xml; charset="utf-8"
Content-Length: 1279