Reference doc for HATEOAS

arialdomartini · Jan 22, 2020 · 360eab2 · 360eab2
1 parent 5cc6c48
commit 360eab2
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 2 deletions.
diff --git a/docs/guidelines.md b/docs/guidelines.md
@@ -22,5 +22,6 @@ We build web services according to [REST](rest.md) on HTTP, aiming to a [high ma
 We strive to adopt a [consistent naming convention](rest.md#naming-conventions).
 
 ## References
-[Microsoft - Web API design](https://docs.microsoft.com/en-us/azure/architecture/best-practices/api-design)
-[Martin Fowler - Richardson Maturity Model](https://martinfowler.com/articles/richardsonMaturityModel.html)
+* [Microsoft - Web API design](https://docs.microsoft.com/en-us/azure/architecture/best-practices/api-design)
+* [Martin Fowler - Richardson Maturity Model](https://martinfowler.com/articles/richardsonMaturityModel.html)
+* [Microsoft - Use HATEOAS to enable navigation to related resources](https://docs.microsoft.com/en-us/azure/architecture/best-practices/api-design#use-hateoas-to-enable-navigation-to-related-resources)
diff --git a/docs/rest.md b/docs/rest.md
@@ -33,6 +33,7 @@ https://mycompany.com/api/orders/12
     "items": "https://mycompany.com/api/orders/12/items"
 }
 ```
+See [Microsoft - Use HATEOAS to enable navigation to related resources](https://docs.microsoft.com/en-us/azure/architecture/best-practices/api-design#use-hateoas-to-enable-navigation-to-related-resources)
 
 * A uniform interface based on HTTP *verbs* (`GET`, `POST`, `DELETE`, etc)