HTTP Response Codes¶
The HTTP response status codes are specified in section 6 of the RFC 2616, Hypertext Transfer Protocol – HTTP/1.1 standard.
The following table lists the more common status codes you may receive:
| Method | Code | Meaning | Resolution |
|---|---|---|---|
| GET | 200 | Resource exists | – |
| 301 | Permanently moved | – | |
| 401 | Authorization error | – | |
| 404 | Not found | – | |
| 410 | No longer exists | – | |
| PUT/POST | 200 | Resource replaced | – |
| 201 | Resource created | – | |
| 204 | No response | – | |
| 301 | Redirect | Usually, missing the trailing slash ‘/’ in the URI | |
| 400 | Invalid data | – | |
| 401 | Authorization error | – | |
| 409 | Resource state conflict | – | |
| 500 | Internal error | Django error; enable debugging to evaluate (see Debug API Errors) | |
| 501 | Method not implemented | – | |
| DELETE | 200 | Resource deleted | – |
| 400 | Resource not deleted | – | |
| 401 | Authorization error | – |
