REST
also: restful, rest api, rest apis, rest endpoint
A common way of designing APIs: each kind of data gets its own web address, and standard actions like "get" or "delete" are used on it.
An architectural style for HTTP APIs. Resources are identified by URLs, like /orders/42, and HTTP methods express intent: GET reads, POST creates, PUT or PATCH updates, DELETE removes. Requests are stateless, and data is usually exchanged as JSON.
A filing cabinet with clearly labeled drawers. Orders drawer, folder 42. You can look at a folder, add one, change one or remove one, and every drawer works the same way.
Most APIs your agent builds or connects to are REST-style. Knowing the convention lets you read a list of endpoints and guess what each does, and notice when one breaks the pattern.
I've added REST endpoints for habits: GET /habits, POST /habits, PATCH /habits/:id and DELETE /habits/:id.
Design a REST API for recipe collections. List each endpoint with its method and what it returns before writing any code.
Thinking REST is a library or product you install. It's a set of conventions for how an API is laid out.