Enverus Authentication

generated: '2026-07-19'
method: searched
source: https://app.enverus.com/direct/#/api/explorer/v2/gettingStarted
docs: https://app.enverus.com/direct/#/api/explorer/v2/gettingStarted
note: >-
  Derived from the documented DirectAccess API v2 authentication flow (Enverus
  developer docs and the community directaccess client). No OpenAPI is published
  publicly (the API explorer and specs sit behind login), so this profile is
  authored from the documented token-exchange behavior rather than derived from
  a spec.
summary:
  types:
  - apiKey
  - oauth2
  api_key_in:
  - header
  oauth2_flows:
  - clientCredentials
schemes:
- name: ApiKey
  type: apiKey
  in: header
  parameter: X-Api-Key
  description: >-
    An Enverus-issued API key is presented on every request (and on the token
    request) via the X-Api-Key header.
- name: ClientCredentials
  type: oauth2
  flow: clientCredentials
  token_url: https://di-api.drillinginfo.com/v2/direct-access/tokens
  description: >-
    A client_id and client_secret are exchanged at the token endpoint (grant
    type client_credentials, HTTP Basic authentication of client_id:client_secret
    plus the X-Api-Key header) for a short-lived bearer access token.
- name: BearerToken
  type: http
  scheme: bearer
  description: >-
    The access token returned by the token endpoint is sent as
    Authorization: Bearer <access_token> on all subsequent dataset queries.
flow:
- step: request-token
  method: POST
  url: https://di-api.drillinginfo.com/v2/direct-access/tokens
  sends: [X-Api-Key header, Basic client_id:client_secret]
  returns: access_token (bearer)
- step: query
  method: GET
  url: https://di-api.drillinginfo.com/v2/direct-access/{dataset}
  sends: [Authorization Bearer access_token, X-Api-Key header]