Synchrony Financial · API Governance Rules
Synchrony Financial API Rules
Spectral linting rules defining API design standards and conventions for Synchrony Financial.
11 Rules
error 3
warn 7
info 1
Rule Categories
credit
operation
paths
post
response
Rules
error
operation-operationId
All operations must have an operationId.
$.paths[*][get,post,put,patch,delete]
error
operation-summary
All operations must have a summary.
$.paths[*][get,post,put,patch,delete]
warn
operation-summary-title-case
Operation summaries must use Title Case.
$.paths[*][get,post,put,patch,delete].summary
error
paths-versioned
All paths must include a version prefix (e.g., /v1/).
$.paths
warn
operation-tags
All operations must have at least one tag.
$.paths[*][get,post,put,patch,delete]
warn
operation-description
All operations should have a description.
$.paths[*][get,post,put,patch,delete]
warn
credit-auth-merchant-id
Credit authorization operations must include merchantId in the request body.
$.paths['/v1/authorizations/*'].post.requestBody.content['application/json'].schema.properties
info
response-schema-ref
Response schemas should use $ref references for reusability.
$.paths[*][*].responses[*].content['application/json'].schema
warn
post-error-response
POST operations should include 400 or 422 error responses.
$.paths[*].post.responses
warn
operation-security
All operations should declare security requirements.
$.paths[*][get,post,put,patch,delete]
warn
paths-kebab-case
Path segments must use kebab-case.
$.paths