Issue OAuth2 client credentials access token

Issues an access token with the OAuth 2.0 client_credentials grant (machine / server-to-server).
Use the access_token as Authorization: Bearer for about one hour. The JWT is HS256
with iss onsched:v3-api, aud api, grant_type=client_credentials, and OAuth Scopes.
It is not a dashboard user session; use POST /v3/auth/token for Supabase refresh tokens.
No x-api-key on later API calls—company is in the JWT. Re-request when expired (~1h).

Send client_id, client_secret, and grant_type=client_credentials in the form (optional scope).
The API also accepts RFC 6749 client authentication via Authorization: Basic (e.g. curl -u); that
is not a separate OpenAPI security scheme—the oauth2 scheme above is for calling other
endpoints
after you obtain a Bearer token from this URL.

Swagger: Use Authorize → oauth2 (client credentials) on /availability and the rest of the API.
For this request, fill the form fields only; this operation sets security: [] so the explorer
does not attach Bearer to the token request.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Form Data
string
enum
required
Allowed:
string

OAuth client ID (omit if using HTTP Basic with the same values).

string

OAuth client secret (omit if using HTTP Basic).

string

Optional space-delimited OAuth Scopes. Only read and write are allowed. Omit or leave blank to receive both. Unknown names return 400.

Responses

401

Unauthorized

Language
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
*/*