HTTP status codes are pretty confusing sometimes.

πŸ”Ή Informational (100–199)
πŸ”Ή Successful (200–299)
πŸ”Ή Redirects (300–399)
πŸ”Ή Client errors (400–499)
πŸ”Ή Server errors (500–599)

Let's talk about them in a bit more detail 🧡 πŸ‘‡πŸ»
πŸ“Œ informational response (1xx)

Informational responses indicate the acceptance and continuation of the requests.
β–ͺ️ 100 Continue

The server tells the client that everything is OK so far keeps sending requests.
β–ͺ️ 101 Switching Protocol

The client requests the server to switch the protocol. This response is sent for the `Upgrade` HTTP header.
β–ͺ️ 103 Early Hints

The server hints the client to preload the resources while the server preparing the data to be returned.
πŸ“Œ Successful Responses (2xx)

As the term suggests, these status codes indicate that the request is successfully received, accepted, and resolved.
β–ͺ️ 200 Ok

This status code indicates the successful HTTP request. It's a standard successful response for GET, POST, PUT, HEAD, and TRACE.
β–ͺ️ 201 Created

This status code is sent by the server to indicates that a new resource has been created. Generally used for the POST and PUT requests.
β–ͺ️ 202 Accepted

Typically used for the async response. The server confirms to the client that the request has been accepted.
β–ͺ️ 203 Non-Authoritative Information

The server usually returns this to indicate that server is a proxy that received this data from its origin. The proxy returns the modified version of the origin's data.
β–ͺ️ 204 No Content

The server indicates that all is good but nothing to return.
β–ͺ️ 205 Reset Content

The server indicates the client to reset the document. Nothing to return as response data.
β–ͺ️ 206 Partial Content

The server returns this code with the partial data that the client asked for with the `Range` HTTP header.
πŸ“Œ Redirection messages (3xx)

The server usually returns a 3xx redirection status code to indicate that some additional action has to be done by the client to fulfill the request.
β–ͺ️ 300 Multiple Choice

The server returns this code when it has multiple options for response.
β–ͺ️ 301 Moved Permanently

Server sends the new URL with a 301 status code if the requested URL has been shifted to new URL.
β–ͺ️ 302 Found

302 indicates that the requested URL has been changed temporarily. Therefore, can't fulfill the request for this moment
β–ͺ️ 303 See Other

Server tells the client to get the desired resource at another URL with a GET request.
β–ͺ️ 304 Not Modified

304 Indicates that the resources are the same since the last visit. In this case, the client can use the cached resources.
β–ͺ️ 307 Temporary Redirect

The server tells the client that you will get the desired resource at another URL with the same request that the client has just made. URL shifting is temporary.
β–ͺ️ 308 Permanent Redirect

The server tells the client that you will get the desired resource at another URL with the same request that the client has just made. URL shifting is permanent.
πŸ“Œ Client Error Responses (4xx)

The server usually returns 4xx status codes if a client request causes some problem.
β–ͺ️ 400 Bad Request

Incorrect syntax or invalid URLs are generally the reason for 400 Bad Request.
β–ͺ️ 401 Unauthorized

The server returns 401 to indicate that the client should authenticate itself before making requests.
β–ͺ️ 403 Forbidden

The client is authenticated but doesn't have permission to access the resource.
β–ͺ️ 404 Not Found

We see a 404 response most often. It means that the requested URL is not valid.
β–ͺ️ 405 Method Not Allowed

The server returns the 405 status code when the request method is valid but not appropriate to get the desired resource.
β–ͺ️ 406 Not Acceptable

In simple terms, the server returns a 406 Not Acceptable response when it does not find any suitable response according to the request.
β–ͺ️ 407 Proxy Authentication Required

The server returns this code when the client must authenticate itself with the proxy.
β–ͺ️ 408 Request Timeout

The server sends this response without the request, indicating that the server would like to suspend the connection.
β–ͺ️ 409 Conflict

The server usually returns this when there is a conflict in the current state of resources.
β–ͺ️ 410 Gone

The resource has been deleted permanently from the server with any redirect URL.
β–ͺ️ 411 Lenght Required

The server indicates that the client must send `Content-Length` to get the resource.
β–ͺ️ 412 Precondition Failed

The server doesn't meet the precondition that the client mentioned in the request headers.
β–ͺ️ 413 Payload Too Large

Request is too large that the server can't handle. In this case, the server might close the connection.
β–ͺ️ 414 URI Too Large

The server returned a 414 code when the URI provided was too long for the server to process.
β–ͺ️ 415 Unsupported Media Type

The server does not support the media type mentioned in the request. For example, the client wants to upload an image as .png, but the server supports the .jpeg media type.
β–ͺ️ 416 Range Not Satisfiable

The server returns a 416 code when the range mentioned in the `Range` HTTP request header is unsatisfactory. For example, asking for a portion of data that doesn't exist.
β–ͺ️ 417 Expectation Failed

The server is not able to provide the relevant data mentioned in the `Expect` HTTP header.
β–ͺ️ 422 Unprocessable Entity

The server returns a 422 status when there are semantic errors in the request.
β–ͺ️ 426 Upgrade Required

The server indicates that the client should use another protocol to fulfill the request. In response, server sends the required protocol in the `Upgrade` header.
β–ͺ️ 428 Precondition Required

The server indicates that the request should be conditional to reduce the chances of conflicts.
β–ͺ️ 429 Too Many Requests

The client has sent too many requests in the given time frame. For example, the server only handles 100 requests per second.
β–ͺ️ 431 Request Header Fields Too Large

Server indicates that the request header is too larger which can't be handled by the server. In this case, the client can reinitiate the request after reducing the sizer of the request header.
β–ͺ️ 451 Unavailable For Legal Reasons

The server can't provide the requested resource due to legal reasons.
πŸ“Œ Server error responses (5xx)

The 5xx status codes indicate that everything is excellent with the request, but an error occurred on the server-side.
β–ͺ️ 500 Internal Server Error

An unexpected situation occurs which server can't handle at this moment.
β–ͺ️ 501 Not Implemented

The server returns 501 when the request is not handled by the server. For example, the client initiates the DELETE request but the server supports only GET and HEAD.
β–ͺ️ 502 Bad Gateway

502 status code indicates when the server got the invalid response while acting as the gateway.
β–ͺ️ 503 Service Unavailable

Usually, when the server is down for maintenance, the server returns 503 indicating server is not ready to handle the request.
β–ͺ️ 504 Gateway Timeout

Server cannot get the response from the origin while acting as a gateway.
β–ͺ️ 505 HTTP Version Not Supported

The server does not support the HTTP protocol version used in the request.
β–ͺ️ 506 Variant Also Negotiates

The server returns the 506 Variant Also Negotiates code when there is an internal configuration error.
β–ͺ️ 507 Insufficient Storage

The server is unable to store the representation needed to complete the request.
β–ͺ️ 508 Loop Detected

The server detected an infinite loop while processing the resource.
β–ͺ️ 510 Not Extended

The server requires some additional extensions in the request to fulfill it.
β–ͺ️ 511 Network Authentication Required

The client needs to authenticate to gain network access.

β€’ β€’ β€’

Missing some Tweet in this thread? You can try to force a refresh
γ€€

Keep Current with RapidAPI

RapidAPI Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @Rapid_API

30 Sep
Want to learn more about API?

Here is the curated list of excellent infographics related to web APIs, request methods, status codes, and much more.

πŸ§΅πŸ‘‡πŸ»
The Client-Server Architecture The Client-Server Architecture
A visual representation of an HTTP-based system. A visual representation of an HTTP-based system.
Read 12 tweets
30 Sep
Key features of RapidAPI Testing πŸ§ͺ

RapidAPI Testing provides you the monitoring and management of your API along with comprehensive testing.

πŸ§΅πŸ‘‡πŸ» RapidAPI Testing provides you the monitoring and management
πŸ“Œ Comprehensive Testing

RapidAPI allows you to create functional API test flows with an interactive UI.

πŸ”Ή End-to-End flows to mimic exact application behavior
πŸ”Ή Create tests using drag and drop editor
This is not enough, RapidAPI creates automatic tests from API definition. We have built-in support for the most widely used API types, REST, SOAP, and GraphQL.
Read 8 tweets
29 Sep
Top five APIs you can use to build a Random Quote Generator web application. πŸ§‘β€πŸ’»

🧡 πŸ‘‡πŸ»
1️⃣ Quotes

- Free multilingual API for famous random quotes in many languages.

πŸ”— RapidAPI.com/martin.svoboda…
2️⃣ Universal Inspirational Quotes

- Get inspirational images, motivational pictures, healing quotes, and more.

πŸ”— RapidAPI.com/HealThruWords/…
Read 6 tweets
28 Sep
Top 10 API-based web development projects you can build using RapidAPI.

A curated list of excellent tutorials. πŸš€

πŸ§΅πŸ‘‡πŸ»
1️⃣ Travel Advisor App

- A great tutorial on building and deploying a Google Maps Travel Companion App using a free API available on RapidAPI.

πŸ”—
2️⃣ Convolutional Networks for Heart Disease Prediction

- In this video, you'll learn how to build convolutional networks that can predict heart disease using RapidAPI.

πŸ”—
Read 12 tweets
28 Sep
Bitcoin, Blockchain, and Cryptocurrency cover a large portion of Web 3.0.

The ultimate goal of Web 3.0 is to provide a more capable, secure, and semantic web.

Here are the Top four APIs that can make Web 3.0 more accessible and manageable. πŸš€

Thread πŸ§΅πŸ‘‡πŸ»
1️⃣ BraveNewCoin

BraveNewCoin API provides the latest and historical cryptocurrency market data. This API has several endpoints which you can choose from.

πŸ”— RapidAPI.com/BraveNewCoin/a…

πŸ“ˆ Popularity: 9.9/10
πŸ•› Latency: 87ms
βœ… Service Level: 100% Homepage of BraveNewCoin API
2️⃣ Blockchain Data

Gives access to more than 20 blockchains: blocks, transactions, transfers, smart contracts, and tokens.

πŸ”— RapidAPI.com/bitquery-bitqu…

πŸ“ˆ Popularity: 8.2/10
πŸ•› Latency: 329ms
βœ… Service Level: 100% Homepage of Blockchain Data API
Read 6 tweets
27 Sep
HTTP headers allow clients and servers to talk to each other and pass extra bits of information or instructions.

Here are the Top Five HTTP headers you might not know about.

Thread πŸ§΅πŸ‘‡πŸ»
1️⃣ Content-Disposition

Content-Disposition header tells the browser to

- Display the content as a web page or as a part of the web page
- Download the content
Suppose you want to download the file that the server returns. This is how you can do it. πŸ‘‡πŸ»

Content-Disposition: attachment; filename="index.html" Code snippet of Content-Disposition HTTP header. Content-Dis
Read 10 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!

:(