Both success and error status are reported to the client by way of the HTTP Status-Line, which contains the HTTP status code. The application-specific error messages are similar to the CLI error messages.
| Status-Line | Description |
|---|---|
| 100 Continue | POST is accepted, 201 should follow |
| 200 OK | Success with response body |
| 201 Created | POST to create a resource success |
| 202 Accepted | POST to create a resource accepted |
| 204 No Content | Success without response body |
| 400 Bad Request | Invalid request message |
| 403 Forbidden | Access to resource denied |
| 404 Not Found | Resource target or resource node not found |
| 405 Method Not Allowed | Method not allowed for target resource |
| 413 Request Entity Too Large | Too-big error |
| 414 Request-URI Too Large | Too-big error |
| 415 Unsupported Media | Not supported media type |
| 500 Internal Server Error | Operation failed. Note: In this case, the response body will contain the application's specific error message. |
| 501 Not Implemented | Unknown operation |
| 503 Service Unavailable | Recoverable server error |