HTTP status codes / 2xx — Success
Success; the client should reset the view or form.
Like 204, but additionally instructs the client to reset the document/form that produced the request. Almost never used by APIs; occasionally seen in form-driven applications.
Treat it like 204 in API clients.
The fastest way to pin down a 205 is to reproduce the exact request and inspect what actually went over the wire — status, headers, timing and body, without your app code in the way. That is what an API client is for; ReqPad does it from your phone, with every request saved to history.
200 OK · 201 Created · 202 Accepted · 203 Non-Authoritative Information · 204 No Content · 206 Partial Content — or the full reference.
Build the request, send it, read status + headers + timing — on your iPhone. Free to start.