Itron · API Governance Rules
Itron API Rules
Spectral linting rules defining API design standards and conventions for Itron.
8 Rules
error 3
warn 4
info 1
Rule Categories
itron
Rules
error
itron-info-contact
Itron OpenAPI specs must publish a contact pointing at the Itron Developer Program.
$.info
warn
itron-info-license
Itron APIs are partner-gated; the license block must be present and named.
$.info.license
warn
itron-summary-title-case
Every operation summary must be in Title Case (per API Evangelist house style).
$.paths.*.*.summary
error
itron-operation-id-camel-case
operationId values must be lowerCamelCase verbs aligned with the starfish-js SDK methods.
$.paths.*.*.operationId
warn
itron-tag-known
Tag names must be drawn from the documented Starfish resource families.
$.paths.*.*.tags[*]
error
itron-bearer-auth-required
Every non-Tokens operation must require bearerAuth.
$.paths[?(!@property.match(/tokens/))].*.security
info
itron-solution-header-present
All data-plane operations should accept the X-Starfish-Solution header so sandbox vs production can be selected (matches the SDK `solution` option).
$.paths[?(!@property.match(/tokens/))].*.parameters[*].name
warn
itron-pagination-cursor-name
Paginated responses must use `next_page` as the cursor field, matching the documented SDK shape.
$.components.schemas.PagedObservationList.properties