Uplight · Authentication Profile

Uplight Authentication

Authentication

Uplight secures its APIs with http-bearer across 1 declared security scheme, as derived from its OpenAPI definitions.

EnergyUnited StatesUtilitiesElectricityGasDemand ResponseDERGridVirtual Power PlantDERMSEnergy EfficiencyCustomer Engagement
Methods: http-bearer Schemes: 1 OAuth flows: API key in:

Security Schemes

bearerToken http
scheme: bearer

Source

Authentication Profile

uplight-authentication.yml Raw ↑
generated: '2026-07-27'
method: probed
source: >-
  Live anonymous probes of https://api.uplight.com (2026-07-27). Not derived from an
  OpenAPI — this repo has none — and not searched from docs, because Uplight publishes no
  public authentication page.
documented_publicly: false
summary:
  types:
  - http-bearer
  api_key_in: []
  oauth2_flows: []
  note: >-
    The only observable fact is that the production gateway demands a bearer token. The
    grant type (client credentials, authorization code, or an issued static token) could
    not be determined anonymously.
schemes:
- name: bearerToken
  type: http
  scheme: bearer
  bearerFormat: unknown
  sources:
  - probe:https://api.uplight.com/
  evidence: >-
    HTTP 401 with body {"errors":[{"message":"Invalid or no token provided"}]} and
    response header server: kong/3.10.0.6-enterprise-edition. Returned for /, /v1,
    /openapi.json, /swagger.json, /mcp, and every /.well-known/ path — the gateway
    rejects before routing, so the 401 describes the edge policy, not any one operation.
discovery:
  openid_configuration: false
  oauth_authorization_server: false
  probes:
  - url: https://api.uplight.com/.well-known/openid-configuration
    status: 401
  - url: https://api.uplight.com/.well-known/oauth-authorization-server
    status: 401
  - url: https://api.uplight.com/.well-known/oauth-protected-resource
    status: 401
  - url: https://uplight.com/.well-known/openid-configuration
    status: 404
  - url: https://docs.uplight.com/.well-known/openid-configuration
    status: 404
  - url: https://auth.uplight.com/.well-known/openid-configuration
    status: '000'
    note: DNS does not resolve.
  - url: https://login.uplight.com/
    status: '000'
    note: DNS does not resolve.
credential_issuance:
  self_serve: false
  gate: partner-only
  note: >-
    Credentials are issued through a commercial relationship — a utility customer or
    contracted ecosystem partner is granted access to the ReadMe portal at
    docs.uplight.com. No public sign-up, no key-issuance form, no sandbox, no trial.
pointer_note: >-
  Deliberately NOT wired as type Authentication in apis.yml. That pointer feeds the
  "authentication documented" check, and Uplight documents nothing publicly — this file
  records what a probe could observe from outside, not a provider-published auth guide.
  Wire the pointer only if Uplight opens an authentication page.

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/uplight-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.