mirror of
https://github.com/adidas/api-guidelines.git
synced 2025-10-25 15:19:19 +00:00
Updates execution/api-keys.md
Auto commit by GitBook Editor
This commit is contained in:
@@ -1,4 +1,4 @@
|
||||
# Loose Coupling
|
||||
In addition to the [robustness principle](core-principles/robustness.md), API consumers (clients) MUST **operate independently** on API implementation's internals. Similarly the API consumers MUST NOT **assume** or **rely on** any knowledge of the API service internal implementation.
|
||||
In addition to the [robustness principle](core-principles/robustness.md), API consumers (clients) **MUST** **operate independently** on API implementation's internals. Similarly the API consumers **MUST NOT** **assume** or **rely on** any knowledge of the API service internal implementation.
|
||||
|
||||
Where available, the clients SHOULD utilize **hypermedia controls as the engine of the application state**, and rely on the **protocol, message and vocabulary semantics**.
|
||||
Where available, the clients **SHOULD** utilize **hypermedia controls as the engine of the application state**, and rely on the **protocol, message and vocabulary semantics**.
|
||||
|
||||
@@ -1,2 +1,5 @@
|
||||
# Client Application Access Control
|
||||
> GOAL: It is imperative to provide a consistent, preferably self-service, way to obtain API access tokens and register new client applications.
|
||||
# Client Application Access
|
||||
> It is imperative to provide a consistent, preferably self-service, way to obtain API access tokens and register new client applications.
|
||||
|
||||
Every API that is publicly available **MUST** be listed in the adidas API developer portal provided by the API Management platform – Mashery. A client developer **MUST** be able to register new client application using the adidas developers portal and required the application key throughout the portal.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user