Build Restful Api's with Asp.Net Core

Learn what an API is, an application programming interface that allows systems to interact. Explore how a RESTful API acts as a messenger, taking requests and returning responses.

Open the studio, create a new project named see wheels API, choose the restful API template, then prepare to explore the project architecture in the next lesson.

Explore the architecture of the ASP.NET Core ERP project, covering the solution window, the program and startup classes, dependency injection, and controllers, and how entity framework configures data flow.

Create a model folder in the EPA project and add a model class with id, title, and price properties to structure API data.

Create a new controller from the empty api controller template, follow the naming convention ending with 'controller', and install packages from the internet.

Add a post method to create a vehicle record by binding the request body to a vehicle object, sending JSON via postman, and updating a shared static list.

Update a record with a put request by passing an id, similar to a post, replacing the item with the updated object, and verify changes with a get.

Demonstrate the http delete request by adding a delete method with an id parameter and a delete attribute to remove a vehicle, then verify with a get call.

Explore the code first approach by defining your classes and letting Entity Framework generate the database and tables for you.

Install the entity framework core and sql server packages in the api project to connect the database, replace the static data with real data, and enable realtime API access.

Create a DbContext class using the code-first approach, configure a DbSet for vehicles, and wire a controller to perform database operations via a connection string.

Register the DbContext in configure services and configure sql server with a connection string, including the server name and initial catalog see wheels db.

Configure the Savills DB context and use ensure created to build the database and schema when missing, with migrations introduced later.

Learn to implement overloaded get methods to fetch all vehicles or a single vehicle using a db context and a find helper, exposing api/vehicles with an id.

Learn to handle post requests in an asp.net core api by adding a vehicle via the db context, saving changes, and testing with postman, with entity framework auto-generating the id.

Learn to handle put requests in a web API by locating a vehicle by id, updating title and price, saving changes, and verifying updates with a get request.

implement and test a delete request in an asp.net core api by locating a vehicle, removing it, saving changes, and verifying deletion with postman and subsequent get requests.

Explore ETP status codes, standard server response codes that indicate why a resource fails to load, with a document attached and a guide to applying codes in the API.

Learn to return appropriate status codes in a GET request using IActionResult, with convenient methods like Ok, BadRequest, NotFound, and the StatusCode overload from the status codes class.

Learn how to use the post method to create records on the server and return the status code 201 created, validated by Postman tests.

Learn how to implement status codes for put requests in ASP.NET Core, return a 200 with a success message, and handle not found scenarios.

Configure delete method status codes in a restful api, returning a 'record deleted' message on success and not found when the record is missing.

Learn how content negotiation works in RESTful APIs, using the Accept header to request JSON or Excel formats, and how to configure the ASP.NET Core Web API to serve formats.

Explore content negotiation in ASP.NET Core, using media type formatters to serve data as JSON or Excel based on the client's Accept header, with JSON as the default when unspecified.

Learn why code first migrations are needed when you add a color property to the vehicle class, because the ensure created method handles only initial creation, not schema changes.

Drop the database before adding the first migration, then prepare to create the database and its schema with migrations in the next lesson.

Implement code-first migrations in ASP.NET Core using the package manager console to add an initial create migration and run update-database to create the database and vehicles endpoint.

Add data to the database via the API and direct SQL edits, verify with GET, and update records with PUT while fixing the color property mapping in the controller.

Explore model validation and why validating input matters. See how missing values in a post request can store nulls and how backend developers enforce validations to ensure data integrity.

Apply data annotations to model validations in a Web API, using required attributes for title, price, and color, and customize error messages to enforce data integrity.

Explore attribute routing in ASP.NET Core by adding HttpGet attributes to methods, observe how two get methods with the same signature cause ambiguity, and learn how routing clarifies API endpoints.

Use attribute routing in a Web API to resolve get method ambiguity, enabling api/vehicles and api/vehicles/{id} routing by annotating the test method with an action name.

Build a RESTful API with ASP.NET Core for a vehicle marketplace, covering user authentication, vehicle listings, search, details with images, posting ads, and data model relations.

Identify the core database tables for the api—user, vehicle, category, and image, and map one-to-many relationships: category to vehicle, vehicle to image, and user to vehicle, with foreign keys.

Add user, vehicle, category, image, and legal models, define properties, and implement one-to-many relationships using Entity Framework conventions to link users to vehicles, vehicles to categories, and vehicles to images.

Register DbSet properties for user, category, and image in the context and prepare migrations. Create the database via migrations, using initial create, then update-database to generate the needed tables.

Explore the categories controller in an ASP.NET Core API, retrieve bikes, cars, and trucks from the categories table using a get method and the database context.

Secure a rest api in an enterprise level application with token-based authentication, then apply authorization to define permissions for web resources.

Learn to implement a register method in an account controller of an asp.net core rest api, including user validation, email uniqueness check, posting new user data, and returning created status.

Hash passwords before storing them, using the authentication plug-in to generate unique hash strings for each password. Verify passwords during login to ensure secure access without exposing plain text.

Learn how JWTs, an open standard, securely transmit information between client and server, verified by a digital signature, and structured as header, payload with claims, and signature.

Implement jwt authentication in a net core api by installing the authentication plugin, configuring services and appsettings with a signing key and token expiry, and enabling authentication before authorization.

Implement a login endpoint that validates user by email, verifies the password against the hash, and issues a JWT access token with claims.

Protect routes in an ASP.NET Core API by applying the authorize attribute to the categories controller or to individual actions, optionally allowing anonymous access, and securing endpoints with JWT authentication.

Use access tokens to authorize resources in the categories controller, sending the token and token type in the header to access the get /categories endpoint.

Implement a protected change password endpoint in ASP.NET Core that uses the access token to verify the user email and save a hashed new password obtained from change password model.

Implement a protected post endpoint to update the user's phone number via a change phone model. Validate the access token, verify the user email, and return a confirmation.

Implement a post method in the accounts controller to upload a user profile image by accepting bytes, validating the user's email from claims, and uploading with the image uploader package.

Implement an edit user profile post method that uploads a profile image as bytes, secures with authorization, and saves the image to wwwroot/images with a GUID filename.