Wispr AI

Wispr AI Incidents API

The Incidents API from Wispr AI — 1 operation(s) for incidents.

Documentation GitHub OpenAPI

Operations 1

GET /api/v1/incidents/status Get Incident Status #

Specifications

⚙

OpenAPI

https://raw.githubusercontent.com/api-evangelist/wispr-ai/refs/heads/main/openapi/wispr-ai-incidents-api-openapi.yml

Work with this as data

Every API 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 apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
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 API

curl "https://apis.io/api/v1/apis/wispr-ai-incidents-api"

All apis

curl "https://apis.io/api/v1/apis?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.

GitHub Google LinkedIn

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

OpenAPI Specification

openapi: 3.2.0
info:
  title: Wispr Backend Analytics Incidents API
  description: Wispr Backend API
  version: 0.5.2
servers:
- url: https://api.wisprflow.ai
  description: Base URL declared by the provider in apis.yml (roadmap#122).
tags:
- name: Incidents
paths:
  /api/v1/incidents/status:
    get:
      tags:
      - Incidents
      summary: Get Incident Status
      description: 'Return the current incident/outage status for the caller''s region.


        No auth required. On any lookup failure the endpoint returns 200 with

        ``client_region="us"`` and ``incident_status=null`` so the pre-login

        screen is never blocked by a status-check error.'
      operationId: get_incident_status
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/IncidentStatusResponse'
components:
  schemas:
    IncidentStatusDetail:
      properties:
        state:
          type: string
          enum:
          - degraded
          - outage
          title: State
        message:
          type: string
          title: Message
        affected_regions:
          items:
            type: string
            enum:
            - us
            - europe
            - apac
          type: array
          title: Affected Regions
        started_at:
          type: string
          format: date-time
          title: Started At
        incident_url:
          type: string
          title: Incident Url
      type: object
      required:
      - state
      - message
      - affected_regions
      - started_at
      - incident_url
      title: IncidentStatusDetail
      description: Active incident details returned in the status response.
    IncidentStatusResponse:
      properties:
        client_region:
          type: string
          enum:
          - us
          - europe
          - apac
          title: Client Region
        incident_status:
          anyOf:
          - $ref: '#/components/schemas/IncidentStatusDetail'
          - type: 'null'
      type: object
      required:
      - client_region
      - incident_status
      title: IncidentStatusResponse
      description: Response for the unauthenticated incident-status endpoint.
  securitySchemes:
    ApiKeyHeaderPatched:
      type: apiKey
      in: header
      name: Authorization
    APIKeyHeader:
      type: apiKey
      in: header
      name: X-API-Key