SAP Sales and Distribution (SD) · API Governance Rules
SAP Sales and Distribution (SD) API Rules
Spectral linting rules defining API design standards and conventions for SAP Sales and Distribution (SD).
17 Rules
error 8
warn 9
Rule Categories
sap
Rules
warn
sap-sd-path-odata-entity-set
SAP OData entity set paths should use PascalCase entity names (A_EntityName pattern)
$.paths[*]~
error
sap-sd-operation-id-camel-case
OperationIds should use camelCase
$.paths[*][get,post,put,patch,delete].operationId
error
sap-sd-has-tags
All operations must have at least one tag
$.paths[*][get,post,put,patch,delete]
error
sap-sd-has-operation-id
All operations must have an operationId
$.paths[*][get,post,put,patch,delete]
error
sap-sd-has-summary
All operations must have a summary
$.paths[*][get,post,put,patch,delete]
warn
sap-sd-summary-title-case
Operation summaries must use Title Case
$.paths[*][get,post,put,patch,delete].summary
warn
sap-sd-has-description
All operations should have a description
$.paths[*][get,post,put,patch,delete]
error
sap-sd-get-response-200
GET operations must have a 200 response
$.paths[*].get
warn
sap-sd-post-response-201
POST create operations should have a 201 or 200 response
$.paths[*].post
warn
sap-sd-delete-response-204
DELETE operations should return 204 No Content
$.paths[*].delete
warn
sap-sd-odata-top-skip-params
SAP OData collection endpoints should support $top and $skip for pagination
$.paths[?([email protected](/\{/))].get.parameters[*].name
warn
sap-sd-info-contact
API info must include contact information
$.info
warn
sap-sd-info-license
API info must include license information
$.info
error
sap-sd-servers-defined
API must define at least one server
$
error
sap-sd-security-defined
API must define security requirements
$
warn
sap-sd-components-schemas-named
Schema component names should use PascalCase
$.components.schemas[*]~
error
sap-sd-no-empty-paths
Path items must define at least one operation
$.paths[*]