Response codes
UMAPI endpoints can return the following response codes.
|
Code |
Description |
|---|---|
|
200 |
Request succeeded, and the response has content. |
|
201 |
Request succeeded, and a new resource was created. |
|
204 |
Request succeeded, and there is no content to send in the response. |
|
400 |
Bad request. The server cannot process the request due to a client error. |
|
401 |
Unauthenticated user. Client must authenticate itself to get the requested response. |
|
403 |
User account does not have access rights to the API or to see the requested site/businessUnit/agentGroup. |
|
404 |
The server cannot find the requested resource, such as a site or business entity. This resource may not exist. |
|
409 |
Cannot update user, because of a request conflict: the user is currently being updated. |
|
413 |
Request is too large for the server to process. |
|
415 |
The request has a media type that the server or resource does not support, so the server is rejecting the request. |
|
422 |
The request was well-formed, but there were validation errors, so it could not be followed. |
|
440 |
Logged out (session expired). |
|
500 |
Internal server error. |
|
501 |
Not implemented or implementation not found. |
|
502 |
Bad gateway. The server, while working as a gateway to get a response needed to handle the request, got an invalid response. |
|
603 |
SQL error. |
For information on the error-response information sent to users, see:
