Interpol · API Governance Rules

Interpol API Rules

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

0 Rules

Spectral Ruleset

aid: interpol
name: Interpol Rules
description: >-
  Validation, governance, and operational rules applied to the INTERPOL
  APIs.json index and the mirrored Notices OpenAPI artifact.
type: company
profile:
  - apis.json
  - openapi
governance:
  source: api-evangelist
  steward: Kin Lane
  visibility: public
rules:
  - id: apisjson-required-fields
    description: APIs.json must include aid, name, description, url, created, modified, and maintainers.
    severity: error
  - id: apisjson-tags-upper-case
    description: All tags must use upper-case first letters.
    severity: warn
  - id: api-baseurl-required
    description: Each documented API should declare a baseURL when known.
    severity: error
  - id: openapi-non-empty
    description: OpenAPI specs must reference real, validated endpoints. Stub or empty specs are not permitted.
    severity: error
  - id: artifact-location
    description: All OpenAPI specs live under openapi/{repo}-openapi.yml.
    severity: error
  - id: openapi-source-attribution
    description: The mirrored Notices OpenAPI is sourced from bundesAPI/interpol-api and must remain attributed.
    severity: info
  - id: sensitive-domain
    description: This API surfaces law-enforcement notice data; downstream tooling should respect Interpol terms of use.
    severity: warn