Guidelines for the API design and development at adidas
adidas API Guidelines
The goal of this document is to facilitate the work and minimize the effort of all API users at adidas while protecting their investment and encouraging API adoption.
These guidelines lay down the foundation for collaboration, stability, and extensibility.
The API Guidelines are split into two main parts:
- General Guidelines
- API type-specific Guidelines
- REST APIs Guidelines
- Asynchronous APIs Guidelines
The general guidelines section discusses the core principles relevant to any kind of API. The API type-specific section further defines the guidelines specific to a given architectural style or API technique (such as REST, Kafka or GraphQL APIs).
How to read the Guidelines
These Guidelines are available for online reading at GitBook its source can be found on GitHub.
The CAPITALIZED words throughout these guidelines have a special meaning:
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC2119.
Refer to RFC2119 for details.
Validating your API Guidelines against OpenAPI Specification
ruleset.md file you can find a digest of API Guidelines rules which you can validating your API description documents with. If you are using OpenAPI Specification as the API description format you can also leverage the
.spectral.yaml ruleset to automatically verify your specification compliance using Spectral.
To install Spectral you will need Node.js and a package manager (npm or yarn).
Note: The version used with the spectal specifictions was 5.3.0
npm install -g @firstname.lastname@example.org # OR yarn global add @email@example.com
Once installed, to verify your OAS file with spectral execute
spectral lint <oas-file> -r <adidas-api-guidelines-folder>/.spectral.yaml where
<adidas-api-guidelines-folder>/.spectral.yaml indicated the location
For further documentation on Spectral refer to their documentation.
Questions & Comments
Please contact firstname.lastname@example.org or email@example.com in case of questions.
Intended Use Cases
This project is intended to provide the guidelines for design & development of APIs at adidas.
adidas is not responsible for the usage of this software for different purposes that the ones described in the use cases.
License and Software Information
© adidas AG
adidas AG publishes this software and accompanied documentation (if any) subject to the terms of the MIT license with the aim of helping the community with our tools and libraries which we think can be also useful for other people. You will find a copy of the MIT license in the root folder of this package. All rights not explicitly granted to you under the MIT license remain the sole and exclusive property of adidas AG.
NOTICE: The software has been designed solely for the purpose of providing API design and development guidelines. The software is NOT designed, tested or verified for productive use whatsoever, nor or for any use related to high risk environments, such as health care, highly or fully autonomous driving, power plants, or other critical infrastructures or services.
If you want to contact adidas regarding the software, you can mail us at firstname.lastname@example.org.
For further information open the adidas terms and conditions page.