Common HTTP Status Codes

Below is a list of common HTTP status codes along with their meanings and example response formats.

200 OK

• Meaning: The HTTP 200 OK successful response status code indicates that a request has succeeded. A 200 OK response is cacheable by default.
• Example Response:

  {
      "message": "Message will be here"
  }
  

202 Accepted

• Meaning: The request has accepted. Publish is started or Floor-Map-Job is received.
• Example Response:

  {
        "message": "Request accepted. Starting to process task.",
        "task_id": "identifier"
  }
  

400 Bad Request

• Meaning: The server could not understand the request due to invalid syntax.
• Example Response:

  {
      "message": "Invalid request data"
  }
  

401 Unauthorized

• Meaning: The request requires user authentication.
• Example Response:

  {
      "message": "Authentication required"
  }
  

403 Forbidden

• Meaning: The server understood the request, but it refuses to authorize it.
• Example Response:

  {
      "message": "Access denied"
  }
  

404 Not Found

• Meaning: The server can not find the requested resource.
• Example Response:

  {
      "message": "Resource not found"
  }
  

409 Conflict

• Meaning: 409 conflict responses are errors sent to the client so that a user might be able to resolve a conflict and resubmit the request.
• Example Response:

  {
      "message": "Content already exists or resource conflict"
  }
  

422 Unprocessable Entity

• Meaning: 422 Unprocessable Entity is used to indicate that the server understands the content type of the request entity, and the syntax of the request entity is correct, but it was unable to process the contained instructions.
• Example Response:

  {
      "message": "The request was well-formed but was unable to be followed due to semantic errors"
  }
  

500 Internal Server Error

• Meaning: The server encountered an unexpected condition that prevented it from fulfilling the request.
• Example Response:

  {
      "message": "An unexpected error occurred"
  }