Expand description
The three sign-in flows and the token machinery they share.
Modules§
- api_key
- API-key sign-in: the simplest method, plus the small conveniences a CLI wants around it (env pickup and a cheap client-side shape check).
- authorization_
code - Browser authorization-code flow with PKCE and a loopback redirect.
- device_
code - Device-code flow (RFC 8628) for headless and remote sign-in.
Constants§
- DEFAULT_
USER_ AGENT - The
User-Agentthe SDK presents on token requests. A CLI may override it viahttp_client_with_user_agent.
Functions§
- http_
client - Build the default HTTP client used for token requests.
- http_
client_ with_ user_ agent - Build an HTTP client with a caller-chosen
User-Agent(some providers key behaviour off it). - refresh
- Exchange a refresh token for a fresh access token at
token_url.