What is REST?: REST API Tutorial A Web API (or Web Service) conforming to the REST architectural style is called a REST API (or RESTful API) 1 The Six Guiding Principles of REST REST is based on some constraints and principles that promote simplicity, scalability, and statelessness in the design The six guiding principles or constraints of the RESTful architecture are:
REST API Best Practices We get the best results when we combine these practices to serve a large dataset and enhance the user experience Nordic’s article on RESTful API pagination is a good resource for exploring the topic further 11 API Security is Not an Afterthought The security of an API is a non-negotiable aspect
How to Design a REST API - Step by Step Guide - REST API Tutorial Learning REST in pieces is one thing while applying all these concepts to real application development is completely another challenge This tutorial will teach us to design REST APIs for a network-based application Please note that the takeaway from this whole exercise is learning how to apply REST principles in the application design process
REST Architectural Constraints - REST API Tutorial REST defines 6 architectural constraints which make any web service - a truly RESTful API i e Uniform interface, Client–server, Stateless, Cacheable, Layered system, Code on demand (optional)
HTTP Methods - REST API Tutorial REST APIs enable you to develop all kinds of web applications having all possible CRUD (create, retrieve, update, delete) operations REST guidelines suggest using a specific HTTP method on a particular type of call made to the server (though technically it is possible to violate this guideline, yet it is highly discouraged) Use the below-given information to find a suitable HTTP method for
Richardson Maturity Model - REST API Tutorial Richardson Maturity Model serves as a reference for assessing and improving the design of RESTful web services It highlights the importance of URI design, HTTP methods, and HATEOAS in achieving different levels of RESTful maturity
REST API URI Naming Conventions and Best Practices RESTful URI should refer to a resource that is a thing (noun) instead of referring to an action (verb) because nouns have properties that verbs do not have – similarly, resources have attributes Some examples of a resource are: Users of the system; User Accounts; Network Devices etc and their resource URIs can be designed as below:
HTTP Status Codes - REST API Tutorial 6 REST Specific HTTP Status Codes 200 (OK) It indicates that the REST API successfully carried out the client’s requested action and that no more specific code in the 2xx series is appropriate
REST API Response Pagination, Sorting and Filtering As a best practice, REST APIs SHOULD support server-side pagination from day one, even for all collections, as adding pagination is a breaking change Learn how to do it
What is an API? - REST API Tutorial An API (the full form is Application Programming Interface) is a contract (or specification) promised by the software which it will honor if other software wants to interact with it for performing business operations API allows two or more software applications to talk to each other through a well-defined computing interface 1 API Example in Real Life