What is REST?

What is REST?

1. architectural style

   • for providing standards between computer systems on the web

2. Accept headers and parameters

   • In the request header, the client sends the type of content that it can receive from the server. This is called a field, and it ensures that the server does not send data that cannot be understood or processed by the client.
   • for example
     • a text file containing HTML would be specified with the type
       • text/html
         • image
           • image/png image/jpeg image/gif
         • audio
           • audio/wavaudio/mpeg

3. Paths

   • Requests must contain a path to a resource on which the operation must be performed. In RESTful APIs
     • routes must be designed to help the client know what is going on.
     • If we are trying to access a single resource, we would have to add a to the path.
     • For example
       • etrieve the item in the resource with the specified one.
         • remove item from resource with the specified.idGET
           • fashionboutique.com/customers/:idcustomersidDELETE fashionboutique.com/customers/:idcustomersid

4. Response codes

   • 200
     • This is the standard response for successful HTTP requests.
   • 201
     • This is the standard response for an HTTP request that resulted in an item being created successfully.
   • 204
     • This is the standard response for successful HTTP requests, where nothing is returned in the response body.
   • 400
     • The request cannot be processed due to incorrect request syntax, oversize, or other client error.
   • 403
     • The client does not have permission to access this resource.
   • 404
     • The resource could not be found at this time. It may have been removed or may not exist yet.

5. Types of requests

   • Requests GET
   • Requests POST
   • Requests PUT
   • Requests DELETE