From e4634ecc2ca3efff5b0bea4785b340e3fae5a4e1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jan=20B=C3=B6hmer?= Date: Thu, 25 Jan 2024 13:22:01 +0100 Subject: [PATCH] Fixed wrong header in API authentication docs This fix issue #494 --- docs/api/authentication.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/api/authentication.md b/docs/api/authentication.md index d30b877d..cb534097 100644 --- a/docs/api/authentication.md +++ b/docs/api/authentication.md @@ -20,8 +20,8 @@ The only method currently available for authentication is to use API tokens: An API token is a long alphanumeric string, which is bound to a specific user and can be used to authenticate as this user, when accessing the API. -The API token is passed via the `Authentication` HTTP header during the API request, like the -following: `Authentication: Bearer tcp_sdjfks....`. +The API token is passed via the `Authorization` HTTP header during the API request, like the +following: `Authorization: Bearer tcp_sdjfks....`. {: .important } > Everybody who knows the API token can access the API as the user, which is bound to the token. So you should treat the