![]() This document is licensed under The Apache License, Version 2.0. The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “NOT RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in BCP 14 ] ] when, and only when, they appear in all capitals, as shown here. ![]() Status of This DocumentThe source-of-truth for the specification is the GitHub markdown file referenced above. Similar to what interface descriptions have done for lower-level programming, the OpenAPI Specification removes guesswork in calling a service. When properly defined via OpenAPI, a consumer can understand and interact with the remote service with a minimal amount of implementation logic. OpenAPI Specification v3.0.3 | Introduction, Definitions, & More OpenAPI Specification v3.0.3 The OpenAPI Specification (OAS) defines a standard, programming language-agnostic interface description for HTTP APIs, which allows both humans and computers to discover and understand the capabilities of a service without requiring access to source code, additional documentation, or inspection of network traffic. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |