Do REST API Standards Exist?

Sharing is Caring

A REST API is a type of API that confirms to the RESTful constraints. REST is designed to take advantage of existing protocols like HTTP.

HTTP is a standard, REST is not. It’s an architectural style that has constraints that guide API design. For an API to be RESTful there are six rules that it needs to follow. The rules are as follows:

  1. Uniform interface
  2. Client–server
  3. Stateless
  4. Cacheable
  5. Layered system
  6. Code on demand (mostly legacy)

REST Standards

With REST there’s no standard, but there are some standards associated with REST such as oAuth and OpenAPI.

oAuth stands for Open Authentication. It’s an open standard for allowing applications to obtain limited access to a user’s information on another website without giving them the password.

OpenAPI is a standard to describe and document REST APIs. It allows us to define the API in a single document and validate the contracts we are creating as we go.

oData is another option for describing and documenting REST APIs. oData is pretty time consuming to set up, but it’s a great option.

OpenAPI, Open Data Protocol (oData), RAML and RSDL are sometimes also called RESTful API Description Languages.

Wrapping It Up

REST is not a standard, it’s a type of architecture. There are two competing standards that are related to REST: OpenAPI, and Open Data Protocol (oData).

Sharing is Caring

Brian is a software architect and technology leader living in Niagara Falls with 13+ years of development experience. He is passionate about automation, business process re-engineering, and building a better tomorrow.

Brian is a proud father of four: two boys, and two girls and has been happily married to Crystal for more than ten years. From time to time, Brian may post about his faith, his family, and definitely about technology.