Signal · API Governance Rules

Signal API Rules

Spectral linting rules defining API design standards and conventions for Signal.

8 Rules error 2 warn 4
View Rules File View on GitHub

Rule Categories

signal

Rules

warn
signal-basic-auth-required
Signal Server API uses Basic authentication with phone number credentials
$.components.securitySchemes[*]
warn
signal-path-param-naming
Signal Server path parameters should follow consistent naming
$.paths[*][*].parameters[?(@.in == 'path')]
error
signal-operation-id-required
All operations must have an operationId
$.paths[*][get,post,put,delete,patch]
error
signal-operation-summary-required
All operations must have a summary
$.paths[*][*]
warn
signal-delete-returns-204
DELETE operations should return 204
$.paths[*].delete.responses
hint
signal-prekey-operations-use-put
Pre-key upload operations should use PUT method
$.paths[?(@property =~ /keys/)][put]
warn
signal-auth-error-response
Operations should define 401 unauthorized response
$.paths[*][get,post,put,delete,patch].responses
hint
signal-base64-key-format
Cryptographic key fields should document Base64 encoding
$.components.schemas[*].properties[?(@.description =~ /base64/i)]

Spectral Ruleset

Raw ↑
extends: spectral:oas
rules:
  # Signal Server uses Basic auth (username:password where username=number, password=signaling key)
  signal-basic-auth-required:
    description: Signal Server API uses Basic authentication with phone number credentials
    message: Signal Server API should use http basic auth scheme
    severity: warn
    given: "$.components.securitySchemes[*]"
    then:
      field: scheme
      function: enumeration
      functionOptions:
        values:
          - basic
          - bearer

  # Signal uses phone number or UUID as primary identifier in paths
  signal-path-param-naming:
    description: Signal Server path parameters should follow consistent naming
    message: Path parameters should use consistent Signal Server naming conventions
    severity: warn
    given: "$.paths[*][*].parameters[?(@.in == 'path')]"
    then:
      field: name
      function: pattern
      functionOptions:
        match: "^(deviceId|sourceDeviceId|destinationServiceId|usernameHash|recipientUUID|attachmentId|packId|stickerNum|messageGuid|keyId)$"

  # All Signal API operations must have operationId
  signal-operation-id-required:
    description: All operations must have an operationId
    message: Operation is missing an operationId
    severity: error
    given: "$.paths[*][get,post,put,delete,patch]"
    then:
      field: operationId
      function: truthy

  # All operations must have a summary in Title Case
  signal-operation-summary-required:
    description: All operations must have a summary
    message: Operation is missing a summary
    severity: error
    given: "$.paths[*][*]"
    then:
      field: summary
      function: truthy

  # Signal Server returns 204 for message sending (no content)
  signal-delete-returns-204:
    description: DELETE operations should return 204
    message: DELETE operations should define a 204 No Content response
    severity: warn
    given: "$.paths[*].delete.responses"
    then:
      field: "204"
      function: truthy

  # Pre-key upload operations should use PUT method
  signal-prekey-operations-use-put:
    description: Pre-key upload operations should use PUT method
    message: Pre-key upload should use PUT (idempotent key upload)
    severity: hint
    given: "$.paths[?(@property =~ /keys/)][put]"
    then:
      function: truthy

  # All responses must define at minimum a 401 error
  signal-auth-error-response:
    description: Operations should define 401 unauthorized response
    message: Operation should define a 401 Unauthorized response
    severity: warn
    given: "$.paths[*][get,post,put,delete,patch].responses"
    then:
      field: "401"
      function: truthy

  # API key base64 parameters should document encoding
  signal-base64-key-format:
    description: Cryptographic key fields should document Base64 encoding
    message: Cryptographic key properties should specify Base64 pattern
    severity: hint
    given: "$.components.schemas[*].properties[?(@.description =~ /base64/i)]"
    then:
      field: pattern
      function: truthy

Work with this as data

Every ruleset 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 spectral rules

4 MCP tools reach this
  • find_rulesBrowse and filter every ruleset 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 ruleset
curl "https://apis.io/api/v1/rules/signal-rules"
All spectral rules
curl "https://apis.io/api/v1/rules?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.

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