Introduction to ASP.NET Core Web API

Welcome to the most powerful, highly-performant, and enterprise-ready backend framework globally: ASP.NET Core. A Web API (Application Programming Interface) allows multiple completely different systems—such as an iOS app, an Android app, an Angular web dashboard, and a Python microservice—to all communicate securely with a single, centralized backend.

1. WHAT is an API? (The Restaurant Analogy)

Imagine you are sitting at a table in a fancy restaurant.

• You (The Client/Frontend): You know what you want to eat, but you don't know how to cook it, nor are you allowed in the kitchen.
• The Kitchen (The Database/Server): Contains all the raw ingredients and the secure logic to prepare the meal.
• The Waiter (The API): You give the waiter your order (an HTTP Request). The waiter takes it to the kitchen, waits for the kitchen to prepare it safely, and then brings the finished meal (an HTTP Response) back to your table.

2. Why ASP.NET Core over Node.js or Python?

3. The Structure of a Web API Project

When you run dotnet new webapi -n MyCompany.Api, you get a highly opinionated but brilliantly structured project.

📁 Controllers/
    📄 WeatherForecastController.cs  <-- The entry points for HTTP requests
📁 Properties/
    📄 launchSettings.json          <-- URLs and ports used during local development
📄 appsettings.json                 <-- Configuration, DB connection strings, and Secrets
📄 Program.cs                       <-- The exact starting point of the application
    

The Modern Program.cs

In the newest .NET versions, the startup file relies entirely on Top-Level statements. Let's break down the anatomy of the pipeline.

var builder = WebApplication.CreateBuilder(args);

// 1. ADD SERVICES TO THE CONTAINER (Dependency Injection)
// Here we register what our application "knows how to do" internally.
builder.Services.AddControllers(); 
builder.Services.AddEndpointsApiExplorer();
builder.Services.AddSwaggerGen();

// 2. BUILD THE APP
var app = builder.Build();

// 3. CONFIGURE THE HTTP REQUEST PIPELINE (Middleware)
// Here we dictate how an incoming network request is processed.
if (app.Environment.IsDevelopment())
{
    app.UseSwagger();
    app.UseSwaggerUI();
}

app.UseHttpsRedirection(); // Force HTTPS
app.UseAuthorization();    // Verify user permissions
app.MapControllers();      // Route the URL to the exact C# Class

// 4. START THE SERVER (Kestrel)
app.Run();

4. Interview Mastery

Q: "ASP.NET Core supports both MVC and Web API. Can you explain the fundamental difference in how they return data?"

Architect Answer: "MVC (Model-View-Controller) is designed to return fully rendered HTML pages directly to a browser. The server does the heavy lifting of mixing data and UI via Razor Views, returning a ViewResult. Web API, however, separates the UI from the data. It returns pure unformatted data, almost exclusively as JSON or XML, by returning an ObjectResult. The client (a React app or iOS app) then assumes complete responsibility for parsing that JSON and rendering its own UI locally."