HTTP Methods & Status Codes Tidbit

In this tidbit I want to touch on different types of HTTP Methods & the types of HTTP status codes you may encounter when consuming APIs in regard to automation.


HTTP Methods:

  • GET = get user info

  • PATCH = update the user

  • HEAD = get only header

  • DELETE = delete the user

  • PUT = replace the user

  • POST = create the user

HTTP Status Codes:

  • 1xx = information

  • 2xx = successful

  • 200 = (OK)

  • 201 = (CREATED)

  • 204 = (NO CONTENT)

  • 3xx = redirection

  • 301 = (MOVED PERMANENTLY)

  • 302 = (FOUND)

  • 304 = (NOT MODIFIED)

  • 4xx = client error

  • 400 = (BAD REQUEST)

  • 401 = (Unauthorized)

  • 403 = (Forbidden)

  • 404 = (Not Found)

  • 5xx = server error

  • 500 = (Internal Server Error)

  • 501 = (Not Implemented)

  • 503 = (Service Unavailable)

To see more check out the <rest> & <api> tags. Cheers!

0 comments

Recent Posts

See All

Troubleshooting FMC Policy Deployment Tidbit

In this tidbit I want to share some tips on how to troubleshoot FMC policy deployment errors. It is important to understand that the policy deployment is broken down into the following phases: Phase

REST vs. RPC APIs

In the post I want to breakdown REST API & RPC API and provide a brief comparison. Let's start with REST. Restful APIs leverage HTTP/S to define the operations on the resources. An example would cont