Skip to content

Instantly share code, notes, and snippets.

@gizipp

gizipp/status-code-explained.md

Created February 27, 2020 00:46
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save gizipp/a637bc38822ba64311a0e947e9a9778d to your computer and use it in GitHub Desktop.
Save gizipp/a637bc38822ba64311a0e947e9a9778d to your computer and use it in GitHub Desktop.
Download ZIP
Status Code Explained
Raw
status-code-explained.md

Status Code Explained

  • 200 – OK Everything is working

  • 201 – CREATED New resource has been created

  • 204 – NO CONTENT The resource was successfully deleted, no response body

  • 304 – NOT MODIFIED The date returned is cached data (data has not changed)

  • 400 – BAD REQUEST The request was invalid or cannot be served. The exact error should be explained in the error payload. E.g. „The JSON is not valid “.

  • 401 – UNATHORIZED The request requires user authentication.

  • 403 – FORBIDDEN The server understood the request but is refusing it or the access is not allowed.

  • 404 – NOT FOUND There is no resource behind the URI.

  • 500 – INTERNAL SERVER ERROR API developers should avoid this error. If an error occurs in the global catch blog, the stack trace should be logged and not returned as a response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment