From 86f551d6fd4076ae77d4db7e240606e898f96b44 Mon Sep 17 00:00:00 2001 From: Josh Hawkins <32435876+hawkeye217@users.noreply.github.com> Date: Sun, 14 Dec 2025 12:37:39 -0600 Subject: [PATCH] tweak headings --- docs/docs/configuration/authentication.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/docs/configuration/authentication.md b/docs/docs/configuration/authentication.md index bbcb7f32c..ad5b3d4d2 100644 --- a/docs/docs/configuration/authentication.md +++ b/docs/docs/configuration/authentication.md @@ -273,11 +273,11 @@ To use role-based access control, you must connect to Frigate via the **authenti ## API Authentication Guide -## Getting a Bearer Token +### Getting a Bearer Token To use the Frigate API, you need to authenticate first. Follow these steps to obtain a Bearer token: -### 1. Login +#### 1. Login Make a POST request to `/login` with your credentials: @@ -295,7 +295,7 @@ You may need to include `-k` in the argument list in these steps (eg: `curl -k - The response will contain a cookie with the JWT token. -### 2. Using the Bearer Token +#### 2. Using the Bearer Token Once you have the token, include it in the Authorization header for subsequent requests: @@ -303,7 +303,7 @@ Once you have the token, include it in the Authorization header for subsequent r curl -H "Authorization: Bearer " https://frigate_ip:8971/api/profile ``` -### 3. Token Lifecycle +#### 3. Token Lifecycle - Tokens are valid for the configured session length - Tokens are automatically refreshed when you visit the `/auth` endpoint