From 3bf23a953537b050bef0ff8b6ed16e0c56a89a59 Mon Sep 17 00:00:00 2001
From: Polo <32060402+Polo2@users.noreply.github.com>
Date: Mon, 2 Dec 2024 10:43:06 +0100
Subject: [PATCH] Readme: fix verb used for /ping endpoint example (#15)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

As we can see in [Bump.sh
documentation](https://developers.bump.sh/operation/operation-get-ping),
endpoint https://bump.sh/api/v1/ping is accessible with verb 'GET', not
'POST'.

I'm glad to contribute to this beautiful project, congratulations on
your new open brick 🚀
---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 5542022..6836d4a 100644
--- a/README.md
+++ b/README.md
@@ -70,14 +70,14 @@ The server verifies the `x-cors-toujours-token` header for every request (name o
 - `path`: Allowed path pattern, supporting path parameters (e.g., `/posts/{post_id}`)
 - `exp`: Token expiration timestamp
 
-E.g.: A client sending a request to `POST https://bump.sh/api/v1/ping`
+E.g.: A client sending a request to `GET https://bump.sh/api/v1/ping`
 via the proxy will need to include an encoded JWT token in
 the `x-cors-toujours-token` header, whose decoded value would look like:
 ```json
 {
   "servers": ["https://bump.sh"],
   "path": "/api/v1/ping",
-  "verb": "POST",
+  "verb": "GET",
   "exp": "2025-01-01T00:00:00Z"
 }
 ```