AlphaSense · API Governance Rules
AlphaSense API Rules
Spectral linting rules defining API design standards and conventions for AlphaSense.
17 Rules
error 6
warn 8
info 3
Rule Categories
info
openapi
operation
paths
schemas
security
servers
tags
Rules
warn
info-title-pattern
Info title should follow "AlphaSense ..." pattern.
$.info.title
warn
info-description-required
Info description must be present and at least 80 characters.
$.info
error
info-version-required
API version must be defined.
$.info
info
info-contact-required
Contact info should be present and link to the developer portal.
$.info
error
openapi-version-3
Must use OpenAPI 3.0.x or 3.1.x.
$
error
servers-must-be-defined
Servers array must be defined and non-empty.
$
error
servers-https-required
All AlphaSense servers must use HTTPS.
$.servers[*]
warn
servers-include-saas-base
At least one server must point at the SaaS gateway api.alpha-sense.com.
$.servers[*]
warn
paths-no-trailing-slash
Paths must not end with a trailing slash.
$.paths
info
paths-include-gql-or-services
AlphaSense exposes either a GraphQL gateway (/gql) or REST surfaces under /services/i/...
$.paths
warn
operation-operationId-required
Every operation should have an operationId.
$.paths[*][*]
warn
operation-summary-title-case
Operation summary should start with an uppercase verb (Title Case).
$.paths[*][*].summary
warn
operation-tags-required
Every operation must declare at least one tag.
$.paths[*][*]
error
security-oauth2-bearer-required
AlphaSense Agent and Utility APIs require OAuth 2.0 bearer tokens.
$.components.securitySchemes
error
security-api-key-header-required
AlphaSense calls require the x-api-key header.
$.components.securitySchemes
warn
schemas-required-fields
Top-level schemas should have a description.
$.components.schemas[*]
info
tags-defined-at-root
Tags used by operations should be defined on the root tags array.
$.tags