Last post Jan 22, 2018 07:56 AM by AngelinaJolie
Jan 19, 2018 11:47 AM|robby32|LINK
Jan 19, 2018 04:46 PM|Khanna Gaurav|LINK
Refer following link
Jan 20, 2018 03:37 AM|robby32|LINK
So after reading that if I break it down by the following.
Lets say I have a company ACME and it provides finding books in a library at certain Universities.
I would write the API (which queries tha database for the required Uni and gets the book . Could be search by catergory , title or other factors)
Then I make this API publicly available and any user can query the API and retrieve the result set.
Is that what it is in a nutshell ?
Jan 20, 2018 06:35 PM|almir_1|LINK
The original paper about RESTFUL APIs was written by Roy Fieldings and discussion is centered around resources that a consumer can request from RESTFUL APIs. REST APIs are not concerned with the data store it can be anything.
APIs (REST or otherwise) are not necessarily publicly available, APIs can be secured and have restricted access.
Jan 22, 2018 07:56 AM|AngelinaJolie|LINK
I would like to understand more
Sir, please refer to this example:
To get a list of a books for a particular author, the client will send a GET request to /api/authors/id/books, where id is the ID of the author.
Add the following method to BooksController.
public IQueryable<BookDto> GetBooksByAuthor(int authorId)
return db.Books.Include(b => b.Author)
.Where(b => b.AuthorId == authorId)
This example is interesting because "books" is treated a child resource of "authors". This pattern is quite common in RESTful APIs.
With regards, Angelina Jolie