Hedgespecialty Com Authentication

generated: '2026-10-29'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://docs.hedgespecialty.com/api/operations/registeroauthclient
sources:
- https://docs.hedgespecialty.com/api/operations/registeroauthclient
- https://docs.hedgespecialty.com/api/operations/startoauthauthorization
- https://docs.hedgespecialty.com/api/operations/startoauthdeviceauthorization
- https://docs.hedgespecialty.com/api/operations/exchangeoauthtoken
description: Hedge uses OAuth 2.0 for authentication.
schemes:
- type: oauth2
  name: OAuth2
  evidence: RFC 6749 authorization endpoint, PKCE (S256) required. Redirects the broker to the portal consent screen; on approval the browser
    returns to your redirect_uri with a single-use code for /oauth/token.
  flows:
  - authorization_code
  - client_credentials
  - device_code
  authorize_url: https://api.hedgespecialty.com/api/v1/oauth/authorize
  how_to_obtain: Register a client via POST /oauth/register to receive a client_id (no client_secret). Use the client_id with the authorization
    endpoint or device authorization endpoint, then exchange the code or device code at POST /oauth/token.
note: The documentation does not specify a header name for sending the access token; typical usage is the Authorization header with a Bearer token.
docs: https://docs.hedgespecialty.com/api/operations/registeroauthclient