Jentic · API Governance Rules
Jentic API Rules
Spectral linting rules defining API design standards and conventions for Jentic.
14 Rules
error 9
warn 5
Rule Categories
jentic
Rules
error
jentic-info-title
API title must include "Jentic".
$.info.title
error
jentic-info-description-required
API info.description is required and must be substantive.
$.info
error
jentic-info-contact-required
API must have a contact entry pointing at Jentic Support.
$.info.contact
error
jentic-server-url-https
All server URLs must use HTTPS.
$.servers[*].url
warn
jentic-server-versioned-path
Production server path must include the /api/v1 prefix.
$.servers[?(@.description == 'Production')].url
error
jentic-operation-id-camel-case
operationId must be camelCase.
$.paths.*.*.operationId
warn
jentic-summary-title-case
Operation summaries must use Title Case.
$.paths.*.*.summary
error
jentic-description-required
Every operation must have a description.
$.paths.*.*
error
jentic-tags-required
Every operation must be tagged with at least one tag.
$.paths.*.*.tags
warn
jentic-tag-allowed-values
Operation tags must come from the canonical Jentic tag set.
$.paths.*.*.tags[*]
error
jentic-api-key-header
API key auth must use the X-JENTIC-API-KEY header.
$.components.securitySchemes.apiKeyAuth
warn
jentic-uuid-pattern
Operation/workflow UUID fields must enforce op_/wf_ prefix.
$.components.schemas..[?(@property === 'uuid')].pattern
warn
jentic-error-response-schema
4xx/5xx responses must reference ErrorResponse.
$.paths.*.*.responses[?(@property.match(/^[45]/))].content.application/json.schema
error
jentic-execution-type-enum
ExecutionRequest.execution_type must be enum operation|workflow.
$.components.schemas.ExecutionRequest.properties.execution_type.enum