From 66971d27009d4b1e6144da3c6f84a6c5da8609b2 Mon Sep 17 00:00:00 2001
From: mrIncompetent <mrIncompetent@users.noreply.github.com>
Date: Wed, 22 Nov 2023 17:40:40 +0200
Subject: [PATCH] Document usage of Authorization header for authentication

The feature has been rolled out to all regions.
Issue: https://github.com/qdrant/cloud-pm/issues/125
---
 qdrant-landing/content/documentation/cloud/authentication.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/qdrant-landing/content/documentation/cloud/authentication.md b/qdrant-landing/content/documentation/cloud/authentication.md
index cebb57c81..906e28e5a 100644
--- a/qdrant-landing/content/documentation/cloud/authentication.md
+++ b/qdrant-landing/content/documentation/cloud/authentication.md
@@ -27,6 +27,11 @@ Our official Qdrant clients for Python, TypeScript, Go, Rust, and .NET all suppo
 curl \
   -X GET https://xyz-example.eu-central.aws.cloud.qdrant.io:6333 \
   --header 'api-key: <provide-your-own-key>'
+
+# Alternatively, you can use the `Authorization` header with the `Bearer` prefix
+curl \
+  -X GET https://xyz-example.eu-central.aws.cloud.qdrant.io:6333 \
+  --header 'Authorization: Bearer <provide-your-own-key>'
 ```
 
 ```python