liveBook · Manning

OpenAPI specification

As explained in .NET in Action, Second Edition

OpenAPI is a machine-readable specification for describing HTTP APIs, including their endpoints, operations, parameters, and representations.

OpenAPI is a machine-readable specification for describing HTTP APIs. Swagger is its predecessor and remains a familiar name through Swagger UI, a browser-based interface for testing API operations. section 5.5

Use OpenAPI tooling to expose and exercise an ASP.NET Core API:

  • Add the Swashbuckle.AspNetCore package to generate OpenAPI documents and expose Swagger UI. section 5.5
  • Select an operation, choose Try It Out, provide parameters, and inspect the response. section 5.5
  • Use the interface to test non-GET operations such as POST, PATCH, and DELETE. section 5.5

How .NET in Action, Second Edition covers it

How deep it goes
Explains terminology and configures document generation and UI exposure, but does not descend into the OpenAPI specification format.
Examples
Uses Catalog API GET, POST, PATCH, and DELETE operations as interactive testing examples.
What it assumes
Assumes an ASP.NET Core HTTP API with controllers and endpoints, while introducing Swagger/OpenAPI terminology and setup.
What you can do after
Operate/configure it through Swashbuckle and Swagger UI to generate API documentation and send test requests.
How it connects
Connects OpenAPI with Swagger, Swagger UI, Swashbuckle, ASP.NET Core, HTTP verbs, and API controllers.

Also explained in

Compare how 12 books explain OpenAPI specification →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of .NET in Action, Second Edition. The section links point to the parts of the book it draws on.