From 8cf5c73f5371daf2cf595fc20da0e944a9bc9efc Mon Sep 17 00:00:00 2001 From: Kaloyan Milev Date: Sun, 30 Aug 2026 16:58:42 +0200 Subject: [PATCH] Fix broken example-API links in resource naming doc --- content/introduction/resourcenaming.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/introduction/resourcenaming.md b/content/introduction/resourcenaming.md index 0813ee3..6fdf685 100644 --- a/content/introduction/resourcenaming.md +++ b/content/introduction/resourcenaming.md @@ -86,9 +86,9 @@ By now you can see how the hierarchy concept works. There aren't any hard and fa ### Other Example APIs Look at some widely used APIs to get the hang of this and leverage the intuition of your teammates to refine your API resource URIs. Some example APIs are: -* Twitter: https://developer.twitter.com/en/docs/api-reference-index -* Facebook: https://developers.facebook.com/docs/reference/api/ -* LinkedIn: https://developer.linkedin.com/apis +* X (Twitter): https://docs.x.com/x-api/overview +* Facebook: https://developers.facebook.com/docs/graph-api/ +* LinkedIn: https://learn.microsoft.com/en-us/linkedin/ ---- * Previous: [HTTP Methods](/introduction/httpmethods.html)