HTTP Response Codes
Code |
Description |
Notes |
---|---|---|
200 |
OK |
Solution execution was successful. This is the most common code used to indicate success. |
201 |
CREATED |
Resource was successfully created. The response body contains the data of the newly created resource. |
204 |
NO CONTENT |
Call executed successfully. The response body is empty. This is used for DELETE operations. |
400 |
BAD REQUEST |
Executing the call would cause an invalid state, such as a domain validation error or missing data. |
401 |
UNAUTHORIZED |
Call executed with a missing or invalid authentication token. |
403 |
FORBIDDEN |
You are not authorized to perform the operation. |
404 |
NOT FOUND |
Requested resource could not be found. |
405 |
METHOD NOT ALLOWED |
The requested URL exists, but the requested HTTP method is not applicable. For example, POST /users/12345 when the API does not support creating resources with a provided ID. |
409 |
CONFLICT |
Fulfilling the request would cause a resource conflict, such as trying to install a Connector that is already installed. |
500 |
INTERNAL SERVER ERROR |
The server threw an exception. Contact Scribe Support if these errors occur. |
See