Mirrors/api-guidelines
1
0
Fork 0
mirror of https://github.com/adidas/api-guidelines.git synced 2025-10-25 15:19:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updates core-principles/apiary.md

Browse Source 
Auto commit by GitBook Editor
This commit is contained in:
apidesigner
2017-01-30 10:48:59 +00:00
parent 9bf3116103
commit e5c26cb2a1
3 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
core-principles/api-first.md
View File

@@ -1,2 +1,2 @@
# API First
API development always starts with API design.
Development of an API MUST always start with API design. API Design MUST be formalized in a form of an API Description.

3
core-principles/apiary.md
View File

@@ -1,2 +1,3 @@
# Apiary
Every API description MUST to be stored in [Apiary](https://apiary.io/) under the ADIDAS GROUP team.
Every API description MUST to be stored in [Apiary](https://apiary.io/) under the ADIDAS GROUP team. Apiary MUST be the single source of truth to learn about existing APIs within the organization.

2
core-principles/openapi-specification.md
View File

@@ -1,2 +1,2 @@
# OpenAPI Specification
Every API has to be described using the [OpenAPI Specification (formerly known as Swagger Specification) version 2.0](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md).
Every API MUST be described using API Description format. The API Description format used MUST be the [OpenAPI Specification (formerly known as Swagger Specification) version 2.0](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md).