Salesforce Flow · API Governance Rules
Salesforce Flow API Rules
Spectral linting rules defining API design standards and conventions for Salesforce Flow.
10 Rules
error 5
warn 4
info 1
Rule Categories
salesforce
Rules
warn
salesforce-flow-operation-summary-title-case
Operation summaries must use Title Case
$.paths[*][*].summary
warn
salesforce-flow-operation-id-camel-case
OperationIds must use camelCase
$.paths[*][*].operationId
warn
salesforce-flow-tags-title-case
All tags must use Title Case
$.paths[*][*].tags[*]
error
salesforce-flow-response-200-description
All 200 responses must have a description
$.paths[*][*].responses['200']
info
salesforce-flow-path-kebab-case
Path segments must use kebab-case or standard Salesforce sObject naming
$.paths[*]~
warn
salesforce-flow-required-fields-documented
Request body schemas should document required fields
$.paths[*][post,put,patch].requestBody.content['application/json'].schema
error
salesforce-flow-contact-info-required
API must have contact information
$.info
error
salesforce-flow-version-present
API must have a version
$.info
error
salesforce-flow-servers-defined
API must define at least one server
$
error
salesforce-flow-security-defined
API must define security schemes
$