Sisense · API Governance Rules
Sisense API Rules
Spectral linting rules defining API design standards and conventions for Sisense.
7 Rules
error 2
warn 4
info 1
Rule Categories
sisense
Rules
warn
sisense-bearer-auth
All Sisense API operations (except login) must use Bearer token authentication
$.paths[?(!@property.match(/login/))].*.security
warn
sisense-title-case-summaries
All operation summaries must use Title Case
$.paths.*.*.summary
error
sisense-camel-case-operation-ids
All operationId values must use camelCase
$.paths.*.*.operationId
warn
sisense-tags-required
All operations must have at least one tag
$.paths.*.*
error
sisense-servers-defined
API must define servers with host variable
$
info
sisense-pagination-params
Collection GET operations should support limit and skip pagination
$.paths[?(!@property.match(/{.*}/))].get.parameters[*].name
warn
sisense-contact-info
API info must include contact information
$.info
Spectral Ruleset
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.
Call it yourself
curl for this page
This ruleset
curl "https://apis.io/api/v1/rules/sisense-rules"
All spectral rules
curl "https://apis.io/api/v1/rules?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.