Hydromancer Leading Hyperliquid Data Provider Authentication

generated: '2026-09-21'
method: searched
source: https://docs.hydromancer.xyz/readme/rest-api.md (REST auth) + https://docs.hydromancer.xyz/readme/get-api-keys.md
docs: https://docs.hydromancer.xyz/readme/rest-api
summary:
  types: [apiKey]
  api_key_in: [header, query]
  oauth2_flows: []
  notes: >-
    Single API-key credential per account. The REST API presents it as an HTTP Bearer token in the
    Authorization header; the WebSocket API accepts the same key as a query parameter on the connection
    URL. There is no OAuth, OIDC or mutual-TLS surface. Keys are issued through manual, personalized
    onboarding (contact data@hydromancer.xyz), not a self-serve dashboard.
schemes:
  - name: rest_bearer_token
    type: apiKey
    in: header
    parameter_name: Authorization
    format: 'Authorization: Bearer YOUR_API_KEY'
    applies_to: Hydromancer REST API (https://api.hydromancer.xyz, POST /info)
    description: >-
      All REST requests must include an Authorization header carrying the account API key as a Bearer
      token. A missing or invalid key returns HTTP 401 with body {"error": "Invalid API key"}.
    sources: [https://docs.hydromancer.xyz/readme/rest-api.md]
  - name: ws_query_api_key
    type: apiKey
    in: query
    parameter_name: null
    applies_to: Hydromancer WebSocket API (wss://api.hydromancer.xyz/ws)
    description: >-
      The WebSocket API authenticates by passing the same account API key as a query parameter on the
      connection URL. The exact parameter name is not stated verbatim in the public docs; the key is
      the same credential used for the REST Bearer token.
    sources: [https://docs.hydromancer.xyz/readme/websocket.md]