Energistics · Authentication Profile

Energistics Authentication

Authentication

Authentication methods published by Energistics for ETP v1.1

Energistics declares 3 security scheme(s) across its OpenAPI definitions.

Data StandardsEnergy IndustryOil & GasNon‑profit ConsortiumData InteroperabilityTechnical Standards
Methods: Schemes: 3 OAuth flows: API key in:

Security Schemes

Bearer http-bearer
Bearer http-bearer
Basic http-basic

Source

Authentication Profile

energistics-authentication.yml Raw ↑
generated: '2026-10-23'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://docs.energistics.org/ETP/ETP_TOPICS/ETP-000-171-0-C-sv1100.html
sources:
- https://docs.energistics.org/ETP/ETP_TOPICS/ETP-000-171-0-C-sv1100.html
- https://docs.energistics.org/ETP/ETP_TOPICS/ETP-000-172-0-C-sv1100.html
- https://docs.energistics.org/ETP/ETP_TOPICS/ETP-000-177-0-C-sv1100.html
- https://docs.energistics.org/ETP/ETP_TOPICS/ETP-000-173-0-C-sv1100.html
description: Authentication methods published by Energistics for ETP v1.1
schemes:
- type: http-bearer
  name: Bearer
  evidence: 'The token MUST be presented using the Bearer schema. The content of the header should look something like this: Authorization: Bearer
    <token>'
  location: header
  header: Authorization
  how_to_obtain: Implementation‑dependent; not specified on the page.
- type: http-bearer
  name: Bearer
  evidence: The token is presented during the WebSocket upgrade request, using either the Authorization header or on the query string as described
    above.
  location: query
  how_to_obtain: Implementation‑dependent; not specified on the page.
- type: http-basic
  name: Basic
  evidence: Basic authentication is as described in RFC-2617 (https://www.ietf.org/rfc/rfc2617.txt) for HTTP connections.
  location: header
  header: Authorization
  how_to_obtain: Standard HTTP Basic credentials (username and password) as defined in RFC‑2617.
docs: https://docs.energistics.org/ETP/ETP_TOPICS/ETP-000-171-0-C-sv1100.html

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact
curl "https://apis.io/api/v1/security/energistics-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.