From 84cb17e3f763c320c4e4a772ba5c8f8d6e95e77c Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Fri, 10 Apr 2026 10:43:19 +0000 Subject: [PATCH] Clarify OAuth token usage on public endpoints Generated-By: mintlify-agent --- apps-and-integrations/oauth.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps-and-integrations/oauth.mdx b/apps-and-integrations/oauth.mdx index e17d779..7e545d2 100644 --- a/apps-and-integrations/oauth.mdx +++ b/apps-and-integrations/oauth.mdx @@ -35,7 +35,7 @@ You must select your scopes when creating your OAuth client, and include them in | `PROFILE_WRITE` | Edit personal info | Updating the authorized user's profile | - Some endpoints like creating, cancelling, and rescheduling bookings are public and do not require any scope. + Some endpoints like creating, cancelling, and rescheduling bookings, as well as slot availability endpoints, are public and do not require any scope. You can still pass an OAuth access token when calling these endpoints — the token is accepted but not required. This means you can use a consistent `Authorization: Bearer ` header across all your API requests without worrying about whether a specific endpoint is public or scoped. ### Team scopes