Error Code

HTTP Status Codes

HTTP status codes are three-digit codes used to indicate the status of the HTTP request-response cycle between the client and server. They are defined by RFC 2616 and extended by various other RFCs such as RFC 2518, RFC 2817, RFC 2295, RFC 2774, and RFC 4918. The first digit of the status code represents one of the five response categories. The message phrases displayed are typical, but alternative readable phrases may be provided. Unless otherwise specified, status codes are part of the HTTP/1.1 standard (RFC 7231).

HTTP 2XX: Request Success

HTTP 200 OK : Request was successful and the expected response headers or data body will be returned with this response.
HTTP 202 Accepted : Used for Controller control-type resource asynchronous processing responses. It indicates that the request has been received. For time-consuming processes, asynchronous handling is typically used to complete the task.
HTTP 204 No Content : Request was successful, but no resource-related status or information will be returned in the response body.
HTTP 206 Partial Content : The server has successfully processed part of a GET request. The response body contains content specified by the Content-Range.

HTTP 3XX : Redirection

HTTP 301 Moved Permanently : Indicates that the resource being accessed has been permanently moved.
HTTP 303 See Other : The requested resource is located at a different URI. Use GET to redirect to the new resource.
HTTP 304 Not Modified : Indicates that the resource has not been modified, meaning the resource on the server is identical to the version cached by the client. No resource body is returned.
HTTP 307 Temporary Redirect : The URI currently cannot provide the requested service. Temporarily redirect to another URI.

HTTP 4XX : Client Errors

HTTP 400 Bad Request : Used for general client-side errors. Indicates a syntax error or incorrect parameters in the request. Specific error details will be included in the response body.
HTTP 401 Unauthorized : Indicates that the request authentication failed.
HTTP 403 Forbidden : The server refuses to allow access to the requested resource, typically due to permission issues or excessive failed requests.
HTTP 404 Not Found : The requested resource could not be found.
HTTP 405 Method Not Allowed : The HTTP method is not supported by the resource (e.g., a POST/DELETE request is not allowed).
HTTP 406 Not Acceptable : The client’s requested resource format is not supported.
HTTP 409 Conflict : Resource state conflict.
HTTP 429 Too Many Requests : The client has sent too many requests in a given period.

HTTP 5XX : Server Errors

HTTP 500 Internal Server Error : A general server-side error indicating an unexpected situation that prevents the server from fulfilling the request. Additional details are usually included in the response body.
HTTP 502 Bad Gateway : Indicates that the service is temporarily unavailable.
HTTP 503 Service Unavailable : Indicates that the server is overloaded or undergoing maintenance and cannot handle the request. The response header will include a Retry-After field indicating the expected downtime duration.

Response Error Codes

Common standard response codes:

Return Code

Return Message Description

OPS40001

[getDemandFormat] Invalid

OPS40002

[contentType] Invalid

OPS40003

Field or customKeys must contain at least one

OPS40004

Incorrect parameter value

PreviousWebhook NextDemo

Last updated 2 months ago

HTTP Status Codes

HTTP 2XX: Request Success

HTTP 200 OK : Request was successful and the expected response headers or data body will be returned with this response.

HTTP 202 Accepted : Used for Controller control-type resource asynchronous processing responses. It indicates that the request has been received. For time-consuming processes, asynchronous handling is typically used to complete the task.

HTTP 204 No Content : Request was successful, but no resource-related status or information will be returned in the response body.

HTTP 206 Partial Content : The server has successfully processed part of a GET request. The response body contains content specified by the Content-Range.

HTTP 3XX : Redirection

HTTP 301 Moved Permanently : Indicates that the resource being accessed has been permanently moved.

HTTP 303 See Other : The requested resource is located at a different URI. Use GET to redirect to the new resource.

HTTP 304 Not Modified : Indicates that the resource has not been modified, meaning the resource on the server is identical to the version cached by the client. No resource body is returned.

HTTP 307 Temporary Redirect : The URI currently cannot provide the requested service. Temporarily redirect to another URI.

HTTP 4XX : Client Errors

HTTP 400 Bad Request : Used for general client-side errors. Indicates a syntax error or incorrect parameters in the request. Specific error details will be included in the response body.

HTTP 401 Unauthorized : Indicates that the request authentication failed.

HTTP 403 Forbidden : The server refuses to allow access to the requested resource, typically due to permission issues or excessive failed requests.

HTTP 404 Not Found : The requested resource could not be found.

HTTP 405 Method Not Allowed : The HTTP method is not supported by the resource (e.g., a POST/DELETE request is not allowed).

HTTP 406 Not Acceptable : The client’s requested resource format is not supported.

HTTP 409 Conflict : Resource state conflict.

HTTP 429 Too Many Requests : The client has sent too many requests in a given period.

HTTP 5XX : Server Errors

HTTP 500 Internal Server Error : A general server-side error indicating an unexpected situation that prevents the server from fulfilling the request. Additional details are usually included in the response body.

HTTP 502 Bad Gateway : Indicates that the service is temporarily unavailable.

HTTP 503 Service Unavailable : Indicates that the server is overloaded or undergoing maintenance and cannot handle the request. The response header will include a Retry-After field indicating the expected downtime duration.