S&P Global · API Governance Rules
S&P Global API Rules
Spectral linting rules defining API design standards and conventions for S&P Global.
12 Rules
error 5
warn 7
Rule Categories
spg
Rules
error
spg-info-title-required
Every S&P Global OpenAPI spec must declare an info.title.
$.info
error
spg-info-version-required
Every S&P Global OpenAPI spec must declare an info.version.
$.info
error
spg-servers-https-only
All Kensho service servers must use HTTPS (e.g., https://kfinance.kensho.com).
$.servers[*].url
warn
spg-server-kensho-domain
Kensho service base URLs should resolve to a *.kensho.com host.
$.servers[*].url
warn
spg-path-segments-snake-case
Path segments use snake_case lowercase per the LLM-ready API convention.
$.paths.*~
warn
spg-versioned-path
All non-metadata paths are versioned (e.g., /api/v1/... or /v3/...).
$.paths.*~
warn
spg-operation-summary-title-case
Operation summaries should use Title Case (first letter of each significant word capitalised).
$.paths.*.*.summary
warn
spg-operation-id-required
Every operation must declare an operationId for SDK/codegen stability.
$.paths.*.*
error
spg-success-response-defined
Every operation must define at least one 2xx response.
$.paths.*.*.responses
warn
spg-security-required
S&P Global APIs require authenticated access (OIDC bearer or keypair JWT).
$
warn
spg-extract-versioned-v3
Kensho Extract paths must be under /v3 (current GA major).
$.paths.*~
error
spg-no-stage-in-host
Production servers must not embed dev/staging/qa/test in the host.
$.servers[*].url