From c68a87cdedd59574a4de46f4da002f59318d6e0a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?K=C3=A9vin=20Commaille?= Date: Wed, 14 May 2025 13:11:52 +0200 Subject: [PATCH] Fix links MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Kévin Commaille --- content/client-server-api/_index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/client-server-api/_index.md b/content/client-server-api/_index.md index 4933eb20..d3a71a70 100644 --- a/content/client-server-api/_index.md +++ b/content/client-server-api/_index.md @@ -439,7 +439,7 @@ endpoints it supports. Most API endpoints require the user to identify themselves by presenting previously obtained credentials in the form of an access token. An access token is typically obtained via the [Login](#login) or -[Registration](#account-registration-and-management) processes. Access tokens +[Registration](#account-registration) processes. Access tokens can expire; a new access token can be generated by using a refresh token. {{% boxes/note %}} @@ -494,7 +494,7 @@ used to generate a new access token and refresh token, the new access and refresh tokens are now bound to the device associated with the initial refresh token. -By default, the [Login](#login) and [Registration](#account-registration-and-management) +By default, the [Login](#login) and [Registration](#account-registration) processes auto-generate a new `device_id`. A client is also free to generate its own `device_id` or, provided the user remains the same, reuse a device: in either case the client should pass the `device_id` in