HTTP status codes / 2xx — Success
226 IM Used
Delta encoding: the response is a diff against a previous version.
What it means
Part of RFC 3229 instance manipulation: the server returns a delta relative to a cached version instead of the full resource. Practically extinct on the public web.
Common causes
- Server answered with a delta (RFC 3229 instance manipulation) because the client sent A-IM — practically extinct
How to debug it
If you ever see this, the server supports delta encoding and your client asked for it via A-IM.
The fastest way to pin down a 226 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.
Related codes
200 OK · 201 Created · 202 Accepted · 203 Non-Authoritative Information · 204 No Content · 205 Reset Content — or the full reference.
Reproduce that 226 in 10 seconds.
Build the request, send it, read status + headers + timing — on your iPhone. Free to start.