Gro Intelligence Authentication

generated: '2026-08-22'
method: searched
source: https://github.com/gro-intelligence/api-client/blob/development/groclient/lib.py
docs: https://gro.readthedocs.io/
status: retired
note: >-
  Gro Intelligence published no OpenAPI, so this profile is NOT derived from a
  spec. It is read from the company's own first-party, MIT-licensed client
  library on its live GitHub organization (gro-intelligence/api-client), where
  every request builder sets the same header. The canonical auth documentation
  (developers.gro-intelligence.com/authentication.html) is dead — the host does
  not resolve — so gro.readthedocs.io is the only surviving published docs
  mirror. The API itself is retired; this records how it worked.
summary:
  types: [http]
  api_key_in: [header]
  oauth2_flows: []
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  in: header
  parameter_name: authorization
  header_example: 'authorization: Bearer <GROAPI_TOKEN>'
  token_type: opaque long-lived API token issued from the Gro web application
  sources:
  - https://github.com/gro-intelligence/api-client/blob/development/groclient/lib.py
  note: >-
    Constructed identically in every endpoint helper in lib.py
    (get_allowed_units, get_available, list_available, lookup_single,
    lookup_batch, get_data_series, stream_data_series, get_top,
    get_source_ranking, get_available_timefrequency, get_data_points):
    `headers = {"authorization": "Bearer " + access_token}`. No other scheme
    appears anywhere in the client.
token_delivery:
  env_var: GROAPI_TOKEN
  note: >-
    The official client and CLI read the token from the GROAPI_TOKEN
    environment variable by default. Tokens were obtained from the Gro web
    application (app.gro-intelligence.com), which no longer resolves — there is
    no longer any way to obtain a credential.
scopes: []
scopes_note: >-
  No OAuth surface and no scope model. Access was a single account-wide bearer
  token, so scopes/ is correctly absent rather than empty.