A10 Networks · API Governance Rules
A10 Networks API Rules
Spectral linting rules defining API design standards and conventions for A10 Networks.
9 Rules
error 4
warn 4
info 1
Rule Categories
a10
Rules
error
a10-info-contact-required
A10 Networks APIs must declare a contact block.
$.info
error
a10-info-license-required
A10 Networks APIs must declare the A10 EULA license.
$.info
error
a10-server-https-only
A10 Thunder servers are always HTTPS — http:// servers are not allowed.
$.servers[*].url
warn
a10-axapi-v3-base-path
All operational paths must begin with /axapi/v3/.
$.paths[?(@property != '/axapi/v3/auth' && @property != '/axapi/v3/logoff')]~
warn
a10-operation-summary-title-case
Operation summaries must use Title Case.
$.paths[*][get,post,put,delete,patch].summary
error
a10-operation-id-camel-case
operationId values must be lowerCamelCase.
$.paths[*][get,post,put,delete,patch].operationId
warn
a10-signature-auth-required
Operations (except sign-on) must require A10Signature.
$.paths[?(@property != '/axapi/v3/auth')][*].security
warn
a10-tag-defined
Every operation must reference at least one tag.
$.paths[*][get,post,put,delete,patch]
info
a10-schema-kebab-case-fields
aXAPI v3 uses kebab-case property names (e.g. virtual-server, ip-address).
$.components.schemas[*].properties[*]~