Comprehensive API design guidelines for REST, asynchronous, and general API development, promoting consistency and API-First adoption.
adidas API Guidelines is a comprehensive set of design principles and rules for creating consistent, high-quality APIs within the adidas organization. It provides structured guidance for REST, asynchronous, and general API development to promote collaboration, stability, and an API-First mindset. The guidelines include automated validation tools to ensure specifications comply with the defined standards.
API designers, developers, and architects at adidas, as well as external teams seeking enterprise-level API design standards for REST and asynchronous APIs.
It offers a unified, organization-wide framework that reduces design inconsistencies and accelerates API development through clear rules and automated linting. The inclusion of Spectral rulesets enables continuous validation, ensuring adherence to best practices without manual oversight.
adidas group API design guidelines
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Includes a Spectral ruleset (adidas-spectral.yaml) to automatically lint OpenAPI and AsyncAPI specifications, reducing manual compliance checks and ensuring adherence to guidelines.
Uses RFC2119 keywords (MUST, SHOULD, MAY) for unambiguous rule interpretation, which enhances consistency and reduces ambiguity across teams.
Provides guidelines for general principles, REST APIs, and asynchronous APIs (e.g., Kafka), addressing multiple architectural styles in one document.
Emphasizes consistency, extensibility, and developer experience to minimize effort and maximize reusability, fostering an API-First mindset across the organization.
Tailored for adidas's internal use, the guidelines may impose unnecessary constraints for more flexible or external projects, limiting adaptability.
Automated validation only works with OpenAPI and AsyncAPI specifications, excluding other common formats like GraphQL or gRPC, which reduces its utility for diverse API ecosystems.
Requires manual installation of Spectral and Node.js for linting, adding initial setup complexity and maintenance burden for teams without existing tooling.