REST stands for:

Representational state transfer - Wikipedia

A little crudite platter for your references. All searchable, so I hope we can skip over spending time rehashing this.

it includes the following methods:

HTTP =Verb=CRUD=Entire Collection (e.g. /customers)Specific Item (e.g. /customers/{id})

POST=Create=201 (Created), 'Location' header with link to /customers/{id} containing new ID.404 (Not Found), 409 (Conflict) if resource already exists..

GET=Read=200 (OK), list of customers. Use pagination, sorting and filtering to navigate big lists.200 (OK), single customer. 404 (Not Found), if ID not found or invalid.

PUT=Update/Replace=405 (Method Not Allowed), unless you want to update/replace every resource in the entire collection.200 (OK) or 204 (No Content). 404 (Not Found), if ID not found or invalid.

PATCH=Update/Modify 405 (Method Not Allowed), unless you want to modify the collection itself.200 (OK) or 204 (No Content). 404 (Not Found), if ID not found or invalid.

DELETE=Delete=405 (Method Not Allowed), unless you want to delete the whole collection—not often desirable.200 (OK). 404 (Not Found), if ID not found or invalid.

programming error = error code 500 (Internal Server Error)

REST APIs have several types of parameters:

• Header parameters: Parameters included in the request header, usually related to authorization.

• Path parameters: Parameters within the path of the endpoint, before the query string (?). These are usually set off within curly braces.

• Query string parameters: Parameters in the query string of the endpoint, after the ?.

**************************************************************

Many of our Composite/Cisco/TIBCO APIs were based on earlier SOAP and web service protocols:

What is the difference between REST API and web API?

While Web API in the time of Web 1.0 was synonymous with SOAP-based web services, today in Web 2.0, the term SOAP is edging towards REST-style web resources.
*****************************************************************