SpectrumOutage API · Authentication Profile

Spectrumoutage Api Authentication

Authentication

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

spectrumoutageinternettvphonemonitoringstatuszip-codetelecomispnetwork-statuscrowdsourced
Methods: http Schemes: 1 OAuth flows: API key in: header

Security Schemes

bearerAuth http
scheme: bearer

Source

Authentication Profile

Raw ↑
generated: '2026-08-11'
method: searched
source: openapi/spectrumoutage-api-openapi.yml
docs: https://api.spectrumoutage.us
summary:
  types:
  - http
  api_key_in:
  - header
  oauth2_flows: []
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  description: API key issued by SpectrumOutage.us. Request at usspectrumoutage@gmail.com
  header: Authorization
  format: 'Authorization: Bearer YOUR_API_KEY'
  sources:
  - openapi/spectrumoutage-api-openapi.yml
  - https://api.spectrumoutage.us
applies_to: >-
  Every operation. The requirement is declared once at the document root (`security: [{bearerAuth: []}]`)
  and no operation overrides it, so there is no anonymous or partially-public endpoint in the v1 contract.
issuance:
  self_serve: false
  channel: email
  contact: usspectrumoutage@gmail.com
  subject_line: API Key Request
  requirements: state your use case and expected traffic
  alternative: >-
    A key can also be obtained by subscribing to the RapidAPI listing
    (https://rapidapi.com/usspectrumoutageus/api/spectrumoutage), where the BASIC plan is free with a
    500,000 request/month hard cap.
  note: >-
    There is no developer signup, no key dashboard, and no rotation or revocation procedure documented.
    Key lifecycle is entirely manual and out of band.
oauth:
  supported: false
  evidence: >-
    No oauth2 or openIdConnect security scheme in the specification;
    /.well-known/oauth-authorization-server, /.well-known/oauth-protected-resource and
    /.well-known/openid-configuration all return 404 on both spectrumoutage.us and api.spectrumoutage.us.
scopes:
  supported: false
  note: >-
    Bearer key auth with no scope model — a key carries the full surface including the POST /reports write
    operation. No scopes artifact is emitted.
failure_modes:
  - status: 401
    condition: Authorization header absent
    body: '{"error": {"message": "Missing API key. Send Authorization: Bearer <key>"}}'
  - status: 403
    condition: key present but not recognised
    body: '{"error": {"message": "Invalid API key."}}'