Foxglove Technologies · OpenAPI Overlay 1.0.0

API Evangelist enhancements for the Foxglove API

6 actions 6 updates update extends openapi/foxglove-technologies-openapi-original.yml
Derived by API Evangelist Built from the contracts Foxglove Technologies publishes. Foxglove Technologies did not publish this file.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-api-evangelist-notex-apievangelist-profilex-apievangelist-harvested-fromx-api-evangelist-conventionsx-api-evangelist-errorsx-api-evangelist-rate-limitsx-api-evangelist-lifecyclex-api-evangelist-webhooks

Targets 5

$.info
$.servers
$.components.securitySchemes.ApiKey
$.components.schemas.Error
$.tags

OpenAPI Overlay

Raw ↑
overlay: 1.0.0
info:
  title: API Evangelist enhancements for the Foxglove API
  version: 1.0.0
extends: openapi/foxglove-technologies-openapi-original.yml
x-generated: '2026-08-16'
x-method: generated
x-source: >-
  Derived from openapi/foxglove-technologies-openapi-original.yml (harvested verbatim
  from https://docs.foxglove.dev/redocusaurus/plugin-redoc-0.yaml) plus the runtime
  semantics captured in conventions/, rate-limits/, errors/ and lifecycle/. The
  harvested spec is never mutated; these are our additive annotations.
actions:
- target: $.info
  update:
    x-apievangelist-profile: https://apis.io/provider/foxglove-technologies
    x-apievangelist-harvested-from: https://docs.foxglove.dev/redocusaurus/plugin-redoc-0.yaml
    x-api-evangelist-conventions: conventions/foxglove-technologies-conventions.yml
    x-api-evangelist-errors: errors/foxglove-technologies-problem-types.yml
    x-api-evangelist-rate-limits: rate-limits/foxglove-technologies-rate-limits.yml
    x-api-evangelist-lifecycle: lifecycle/foxglove-technologies-lifecycle.yml
    x-api-evangelist-webhooks: asyncapi/foxglove-technologies-webhooks.yml
- target: $.info
  update:
    x-operation-ids-missing: >-
      No operation in this specification declares an operationId. Tooling that
      generates clients, workflows or agent tools from this document must synthesize
      identifiers from method+path, and every downstream API Evangelist artifact
      binds to `METHOD /path` for that reason.
- target: $.servers
  update:
    x-api-evangelist-note: >-
      api.foxglove.dev is the production host despite the .dev TLD; the spec's own
      server description reads "Production".
- target: $.components.securitySchemes.ApiKey
  update:
    x-key-prefix: fox_sk_
    x-capability-model: >-
      Each operation's security requirement names the API key capability it needs
      (e.g. devices.list). 48 distinct capabilities are declared across the spec;
      see authentication/foxglove-technologies-authentication.yml.
    x-admin-only: Only organization admins can create an API key.
- target: $.components.schemas.Error
  update:
    x-error-envelope: >-
      Foxglove returns a flat {"error": "<message>"} envelope, not RFC 9457
      application/problem+json.
- target: $.tags
  update:
    x-api-evangelist-note: >-
      The Imports tag is deprecated in favour of Recordings; all three of its
      operations carry deprecated:true in the source spec.

Work with this as data

Every overlay 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 openapi overlays

4 MCP tools reach this
  • find_overlaysBrowse and filter every overlay 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 overlay
curl "https://apis.io/api/v1/overlays/foxglove-technologies-api-overlay"
All openapi overlays
curl "https://apis.io/api/v1/overlays?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.