MockFoxAdvertise

HTTP 207 Multi-Status

Updated Free mock REST & WebSocket APIs

HTTP 207 Multi-Status — A WebDAV response whose XML body holds a separate status for each of several resources.

Class
2xx Success
Defined in
RFC 4918 (WebDAV)
Official
Yes (IANA registry)
Cacheable by default
No (unless Cache-Control/Expires say so)

Try it: get a real 207 response

Our test endpoint answers every request with 207 Multi-Status.

curl -i https://mockfox.dev/api/status/207

Use it in tests, health-check monitors or to see how your client handles a 207. Add ?delay=2000 to slow it down.

What does HTTP 207 mean?

Returned by WebDAV methods such as PROPFIND, PROPPATCH, COPY and MOVE that act on many resources at once. The body is a <multistatus> XML document with one <response> per resource, each carrying its own status line — so a 207 can contain failures. Some JSON batch APIs borrow 207 for the same purpose.

Handling 207

  1. Visitors: Nothing to fix — this is a success status.
  2. Developers: Make sure clients handle this status as success (response.ok is true for 200–299) and know whether to expect a body.

Example 207 response

HTTP/1.1 207 Multi-Status
Content-Type: application/json

{"status":207,"error":"Multi-Status"}

2xx Success: The request was received, understood and accepted. See the full list of HTTP status codes.

Related status codes

Related tools

Frequently asked questions

What does HTTP 207 Multi-Status mean?

A WebDAV response whose XML body holds a separate status for each of several resources.

Is 207 an error?

No. 207 is a success status.

Where is 207 defined?

In RFC 4918 (WebDAV). It's listed in the IANA HTTP Status Code Registry.

How can I test how my app handles a 207?

Call https://mockfox.dev/api/status/207 — it responds with 207 to any method, with CORS enabled. Add ?delay=2000 to simulate a slow response.