Canonical

Canonical Signals API

The signals API from Canonical — 1 operation(s) for signals.

Documentation GitHub OpenAPI

Operations 1

POST /v1/signals Send a signal to services #

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/canonical-signals-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: Pebble Signals API
  version: v1
tags:
- name: Signals
paths:
  /v1/signals:
    post:
      summary: Send a signal to services
      tags:
      - Signals
      description: Send a signal to each of the specified services.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                signal:
                  type: string
                  description: The signal to send. For example, "SIGHUP", "SIGINT", "SIGKILL".
                services:
                  type: array
                  description: List of service names to send the signal to.
                  items:
                    type: string
                  minItems: 1
              required:
              - signal
              - services
            example:
              signal: SIGHUP
              services:
              - svc1
      responses:
        '200':
          description: Signal sent successfully.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PostSignalsResponse'
              example:
                type: sync
                status-code: 200
                status: OK
                result: true
      operationId: postV1Signals
      x-operation-id-source: derived
components:
  schemas:
    PostSignalsResponse:
      allOf:
      - $ref: '#/components/schemas/BaseResponse'
      - type: object
        properties:
          result:
            type: boolean
            const: true
    BaseResponse:
      type: object
      properties:
        type:
          type: string
          description: Response type, "sync".
        status-code:
          type: integer
          description: HTTP response status code.
        status:
          type: string
          description: 'The description of the HTTP status code.


            See the [IANA list](https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml).

            '