All hungover contracts such as openapi, asyncapi or data product specifications
project
│ README.md
│
└───domain01
│ │ README.md
│ │ Requirements
│ │ DomainModel
│ └───api
│ │ domain01.oas.0.1.yml
│ │ domain01_oas_0_1.html
│ │ ...
│ └───events
│ │ domain01.asyncapi.0.1.yml
│ │ domain01_asyncapi_0_1.html
│ │ ...
│ └───dataproduct
│ │ domain01.datacontract.0.1.yml
│ │ domain01.datacontract.0.1.html
│ │ ...
│
└───domain02
│ │ README.md
│ │ Requirements
│ │ DomainModel
│ └───api
│ │ domain02.oas.0.1.yml
│ │ domain02_oas_0_1.html
│ │ ...
│ └───events
│ │ domain02.asyncapi.0.1.yml
│ │ domain02_asyncapi_0_1.html
│ │ ...
│ └───dataproduct
│ │ domain02.datacontract.0.1.yml
│ │ domain02.datacontract.0.1.html
│ │ ...
│
- HTTP - Hypertext Transfer Protocol
- REST - Representational State Transfer
- URI - Uniform Resource Identifier
- 1xx Informational
- 2xx Success
- 3xx Redirection
- 4xx Client Error
- 5xx Server Error
openapi: 3.0.0
security:
- mySecurityRule: [ ]
info:
title: Sample API
description: Optional multiline or single-line description in [CommonMark](http://commonmark.org/help/) or HTML.
version: 0.1.0
servers:
- url: http://api.example.com/v1
description: Optional server description, e.g. Main (production) server
- url: http://staging-api.example.com
description: Optional server description, e.g. Internal staging server for testing
paths: ## Paths Object
/users: ## Path Item Object has GET, POST etc
get: ## Operation Object has a summary description etc
summary: Returns a list of users.
description: Optional extended description in CommonMark or HTML.
responses: ## Responses Object as 200, 404 etc
'200': ## Response Object has description, content etc
description: A JSON array of user names
content:
application/json:
schema:
type: array
items:
type: string
components:
securitySchemes:
mySecurityRule:
type: http
scheme: bearer