Home
Microsoft Visio
Microsoft Visio API Rules
Microsoft Visio API Rules
Spectral linting rules defining API design standards and conventions for Microsoft Visio.
24 Rules
error 12
warn 12
Rule Categories
error
get
info
no
openapi
operation
parameter
path
response
schema
security
servers
Rules
error
info-title-must-contain-microsoft-visio
Info title must contain 'Microsoft' or 'Visio'
$.info.title
error
info-description-required
Info description is required
$.info
error
info-version-required
Info version is required
$.info
error
openapi-version-3
Must use OpenAPI 3.x
$.openapi
error
servers-must-be-defined
Servers array must be defined
$
error
servers-https-required
All server URLs must use HTTPS
$.servers[*].url
error
operation-operationid-required
Every operation must have an operationId
$.paths[*][get,post,put,patch,delete]
error
operation-summary-required
Every operation must have a summary
$.paths[*][get,post,put,patch,delete]
warn
operation-summary-prefix
Operation summaries should start with 'Microsoft Visio'
$.paths[*][get,post,put,patch,delete].summary
error
operation-tags-required
Every operation must have at least one tag
$.paths[*][get,post,put,patch,delete]
warn
operation-operationid-camel-case
operationId should use camelCase
$.paths[*][get,post,put,patch,delete].operationId
warn
parameter-description-required
Parameters must have a description
$.paths[*][get,post,put,patch,delete].parameters[*]
error
response-success-required
Every operation must define a success response
$.paths[*][get,post,put,patch,delete].responses
warn
response-401-recommended
Operations should define a 401 Unauthorized response
$.paths[*][get,post,put,patch,delete].responses
error
security-global-defined
Global security must be defined
$
error
get-no-request-body
GET operations must not have a request body
$.paths[*].get
warn
servers-expected-domain
Server URLs should be on the microsoft.com domain.
$.servers[*].url
warn
path-params-casing
Path parameters should be kebab-case (the dominant convention in this API).
$.paths[*].parameters[?(@.in=='path')].name
warn
schema-names-casing
Component schema names should be PascalCase (the dominant convention in this API).
$.components.schemas
warn
schema-properties-casing
Schema properties should be snake_case (the dominant convention in this API).
$.components.schemas[*].properties
warn
security-schemes-defined
Security schemes should be defined in components.
$.components
warn
error-schema-defined
A shared error schema (ErrorResponse) should be defined for error payloads.
$.components.schemas
warn
operation-documents-404
Operations should document a 404 response (documented on 100% of this API's operations).
$.paths[*][get,post,put,patch,delete].responses
warn
no-empty-descriptions
Descriptions must not be empty strings.
$..description
Spectral Ruleset
# authorship: generated by API Evangelist tooling. Stamped 2026-08-18
# on the file's own generator header (roadmap#64). An unmarked file is
# NOT assumed to be ours -- absence of evidence was never stamped.
x-method: generated
# microsoft-visio — Spectral ruleset (strengthened)
# Plain Spectral. Existing hand-authored rules preserved; measured rules added
# from this provider's own OpenAPI conventions by strengthen_ruleset.py,
# then self-validated against the spec.
#
# Provenance:
# - servers-https-only: 100% of servers already https (error)
# - servers-expected-domain: 1/1 servers on microsoft.com
# - path-params-casing: kebab @ 100% (n=18)
# - operationid-casing: camel @ 100% (n=8)
# - schema-names-casing: pascal @ 100% (n=12)
# - schema-properties-casing: snake @ 97% (n=29)
# - security: global (root) — NOT emitting operation-security-required
# - error-schema-defined: ErrorResponse
# - operation-documents-401: 100% adherence
# - operation-documents-404: 100% adherence
# - merge: kept 16 existing, added 8 measured, upgraded 0
# - added: servers-expected-domain, path-params-casing, schema-names-casing, schema-properties-casing, security-schemes-defined, error-schema-defined, operation-documents-404, no-empty-descriptions
extends:
- spectral:oas
rules:
info-title-must-contain-microsoft-visio:
description: Info title must contain 'Microsoft' or 'Visio'
given: $.info.title
severity: error
then:
function: pattern
functionOptions:
match: (Microsoft|Visio)
info-description-required:
description: Info description is required
given: $.info
severity: error
then:
field: description
function: truthy
info-version-required:
description: Info version is required
given: $.info
severity: error
then:
field: version
function: truthy
openapi-version-3:
description: Must use OpenAPI 3.x
given: $.openapi
severity: error
then:
function: pattern
functionOptions:
match: ^3\.
servers-must-be-defined:
description: Servers array must be defined
given: $
severity: error
then:
field: servers
function: truthy
servers-https-required:
description: All server URLs must use HTTPS
given: $.servers[*].url
severity: error
then:
function: pattern
functionOptions:
match: ^https://
operation-operationid-required:
description: Every operation must have an operationId
given: $.paths[*][get,post,put,patch,delete]
severity: error
then:
field: operationId
function: truthy
operation-summary-required:
description: Every operation must have a summary
given: $.paths[*][get,post,put,patch,delete]
severity: error
then:
field: summary
function: truthy
operation-summary-prefix:
description: Operation summaries should start with 'Microsoft Visio'
given: $.paths[*][get,post,put,patch,delete].summary
severity: warn
then:
function: pattern
functionOptions:
match: ^Microsoft Visio
operation-tags-required:
description: Every operation must have at least one tag
given: $.paths[*][get,post,put,patch,delete]
severity: error
then:
field: tags
function: truthy
operation-operationid-camel-case:
description: operationId should use camelCase
given: $.paths[*][get,post,put,patch,delete].operationId
severity: warn
then:
function: pattern
functionOptions:
match: ^[a-z][a-zA-Z0-9]*$
parameter-description-required:
description: Parameters must have a description
given: $.paths[*][get,post,put,patch,delete].parameters[*]
severity: warn
then:
field: description
function: truthy
response-success-required:
description: Every operation must define a success response
given: $.paths[*][get,post,put,patch,delete].responses
severity: error
then:
function: schema
functionOptions:
schema:
anyOf:
- required:
- '200'
- required:
- '201'
- required:
- '204'
response-401-recommended:
description: Operations should define a 401 Unauthorized response
given: $.paths[*][get,post,put,patch,delete].responses
severity: warn
then:
field: '401'
function: truthy
security-global-defined:
description: Global security must be defined
given: $
severity: error
then:
field: security
function: truthy
get-no-request-body:
description: GET operations must not have a request body
given: $.paths[*].get
severity: error
then:
field: requestBody
function: falsy
servers-expected-domain:
description: Server URLs should be on the microsoft.com domain.
severity: warn
given: $.servers[*].url
then:
function: pattern
functionOptions:
match: microsoft\.com
path-params-casing:
description: Path parameters should be kebab-case (the dominant convention in this API).
severity: warn
given: $.paths[*].parameters[?(@.in=='path')].name
then:
function: casing
functionOptions:
type: kebab
schema-names-casing:
description: Component schema names should be PascalCase (the dominant convention in this API).
severity: warn
given: $.components.schemas
then:
field: '@key'
function: casing
functionOptions:
type: pascal
schema-properties-casing:
description: Schema properties should be snake_case (the dominant convention in this API).
severity: warn
given: $.components.schemas[*].properties
then:
field: '@key'
function: casing
functionOptions:
type: snake
security-schemes-defined:
description: Security schemes should be defined in components.
severity: warn
given: $.components
then:
field: securitySchemes
function: truthy
error-schema-defined:
description: A shared error schema (ErrorResponse) should be defined for error payloads.
severity: warn
given: $.components.schemas
then:
field: ErrorResponse
function: truthy
operation-documents-404:
description: Operations should document a 404 response (documented on 100% of this API's operations).
severity: warn
given: $.paths[*][get,post,put,patch,delete].responses
then:
field: '404'
function: truthy
no-empty-descriptions:
description: Descriptions must not be empty strings.
severity: warn
given: $..description
then:
function: truthy
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.
All 92 tools →
Call it yourself
curl for this page
This ruleset
curl "https://apis.io/api/v1/rules/microsoft-visio-spectral-rules"
All spectral rules
curl "https://apis.io/api/v1/rules?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms .
A second provider on the same verified email joins the account you already have.