Mock XML endpoint returning HTTP 422

Live demo endpoint

Any method, any path. Returns 422 Unprocessable Content with Content-Type: application/xml. OPTIONS returns 204 with CORS headers.

Call it with curl

curl -i https://demo-xml-422.supercrontab.com/

Call it with fetch

const res = await fetch("https://demo-xml-422.supercrontab.com/");
console.log(res.status); // 422
const body = await res.text();

What HTTP 422 Unprocessable Content means

When you see it

The request was well formed but failed validation: an email without @, a date in the past, a value out of range.

What a client should do

Show the validation errors to the user and fix the payload. Retrying the same body cannot succeed.

Retry?

No

Sample response body

<?xml version="1.0" encoding="UTF-8"?>
<response>
  <ok>true</ok>
  <id>42</id>
</response>

Common in SOAP, payment and legacy enterprise APIs. Good for testing XML parsers and namespaces.

Questions