Librato · Authentication Profile

Librato Authentication

Authentication

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

CompanyDeveloper ToolsMonitoringMetricsObservabilityTime SeriesAlertingDashboardsAnalyticsRetired
Methods: http Schemes: 1 OAuth flows: API key in:

Security Schemes

basicAuth http
scheme: basic

Source

Authentication Profile

librato-authentication.yml Raw ↑
generated: '2026-07-19'
method: searched
source: https://github.com/librato/api-docs/blob/master/source/includes/_authentication.md
docs: https://github.com/librato/api-docs/blob/master/source/includes/_authentication.md
status: retired
summary:
  types:
  - http
  http_schemes:
  - basic
  api_key_in: []
  oauth2_flows: []
  transport: https-only
schemes:
- name: basicAuth
  type: http
  scheme: basic
  description: 'HTTP Basic authentication is required on every request. The username is the
    email address used to create the Librato Metrics account; the password is an API token
    issued from the account tokens page. All requests must be sent over HTTPS — a plaintext
    request is rejected with 403 and the error message "Please use secured connection
    through https!".'
  credential_user: account email address
  credential_password: API token
  token_management: https://metrics.librato.com/tokens
  sources:
  - https://github.com/librato/api-docs/blob/master/source/includes/_authentication.md
notes:
- Credentials may alternatively be embedded in the URL (https://user:token@metrics-api.librato.com/v1/metrics);
  because the user is an email address the "@" must be percent-encoded as %40.
- 'API tokens are themselves managed through the API: the /v1/api_tokens resource supports
  create, retrieve, update, delete and list.'
- No OAuth 2.0, OpenID Connect, mTLS or scoped-permission surface was ever documented for
  this API, so no scopes/ artifact applies.
- The authenticating host metrics-api.librato.com no longer resolves; this profile is a
  historical record.