We provide RESP API module for uHotelBooking script. There are site admins or hotel owners who can access protected site data. REST API for uHotelBooking reservation system. REST is the underlying architectural principle of the web. The amazing thing about the web is the fact that clients (browsers) and servers can interact in complex ways without the client knowing anything beforehand about the server and the resources it hosts. The key constraint is that the server and client must both agree on the media used, which in the case of the web is HTML. An API that adheres to the principles of REST does not require the client to know anything about the structure of the API. Rather, the server needs to provide whatever information the client needs to interact with the service. An HTML form is an example of this: The server specifies the location of the resource, and the required fields. The browser doesn\'t know in advance where to submit the information, and it doesn\'t know in advance what information to submit. Both forms of information are entirely supplied by the server. (This principle is called HATEOAS.) So, how does this apply to HTTP, and how can it be implemented in practice? HTTP is oriented around verbs and resources. The two verbs in mainstream usage are GET and POST, which I think everyone will recognize. However, the HTTP standard defines several others such as PUT and DELETE. These verbs are then applied to resources, according to the instructions provided by the server. We provide RESP API module for uHotelBooking script. There are site admins or hotel owners who can access protected site data.