Home
Advance Auto Parts
Advance Auto Parts API Rules
Advance Auto Parts API Rules
Spectral linting rules defining API design standards and conventions for Advance Auto Parts.
38 Rules
error 16
warn 16
info 6
Generated by API Evangelist
Written by API Evangelist tooling for Advance Auto Parts's APIs. It is a starting point, not a ruleset Advance Auto Parts publishes or enforces.
Rule Categories
delete
error
examples
get
info
no
openapi
operation
parameter
paths
query
request
response
schema
security
servers
vehicle
Rules
warn
info-title-aap-prefix
API title must start with "Advance Auto Parts"
$.info.title
error
info-description-required
API must have a description
$.info
error
info-version-required
API must declare a version
$.info
warn
info-contact-required
API should include contact information
$.info
error
openapi-version-3
Must use OpenAPI 3.x
$
error
servers-defined
API must define servers
$
error
servers-https
Server URLs must use HTTPS
$.servers[*].url
warn
servers-description
Servers should have descriptions
$.servers[*]
warn
paths-no-trailing-slash
Paths must not have trailing slashes
$.paths[*]~
info
paths-lowercase-kebab
Path segments should use lowercase and hyphens
$.paths[*]~
error
operation-summary-required
Operations must have summaries
$.paths[*][get,post,put,patch,delete]
warn
operation-summary-aap-prefix
Summaries should start with "Advance Auto Parts"
$.paths[*][get,post,put,patch,delete].summary
error
operation-description-required
Operations must have descriptions
$.paths[*][get,post,put,patch,delete]
error
operation-id-required
Operations must have operationIds
$.paths[*][get,post,put,patch,delete]
warn
operation-id-camelcase
operationId should use camelCase
$.paths[*][get,post,put,patch,delete].operationId
error
operation-tags-required
Operations must have tags
$.paths[*][get,post,put,patch,delete]
error
parameter-description-required
Parameters must have descriptions
$.paths[*][*].parameters[*]
error
parameter-schema-required
Parameters must have schemas
$.paths[*][*].parameters[*]
warn
request-body-description
Request bodies should have descriptions
$.paths[*][post,put,patch].requestBody
error
response-success-required
Operations must define 2xx responses
$.paths[*][get,post,put,patch,delete]
warn
response-auth-defined
Operations should define 401 Unauthorized response
$.paths[*][get,post,put,patch,delete].responses
error
response-description-required
Responses must have descriptions
$.paths[*][*].responses[*]
warn
schema-description
Component schemas should have descriptions
$.components.schemas[*]
warn
schema-type-defined
Schemas should define a type
$.components.schemas[*]
info
schema-properties-camelcase
Schema property names should use camelCase
$.components.schemas[*].properties[*]~
error
security-schemes-defined
API must define security schemes
$.components
warn
security-global-defined
API should define global security
$
error
get-no-request-body
GET operations must not have request bodies
$.paths[*].get
info
delete-returns-204
DELETE operations should return 204 No Content
$.paths[*].delete.responses
error
no-empty-descriptions
Descriptions must not be empty
$..description
info
examples-encouraged
Responses should include examples
$.paths[*][get,post,put,patch,delete].responses[*].content[*]
info
vehicle-fitment-documented
Fitment endpoints should document year/make/model parameters
$.paths[/vehicles*][get].parameters[*].name
warn
servers-expected-domain
Server URLs should be on the advanceautoparts.com domain.
$.servers[*].url
warn
query-params-casing
Query parameters should be snake_case (the dominant convention in this API).
$.paths[*][get,post,put,patch,delete].parameters[?(@.in=='query')]
warn
schema-names-casing
Component schema names should be PascalCase (the dominant convention in this API).
$.components.schemas
info
schema-properties-casing
Schema properties should be snake_case (the dominant convention in this API).
$.components.schemas[*].properties
warn
error-schema-defined
A shared error schema (ErrorResponse) should be defined for error payloads.
$.components.schemas
warn
operation-documents-401
Operations should document a 401 response (documented on 86% of this API's operations).
$.paths[*][get,post,put,patch,delete].responses
Spectral Ruleset
# authorship: generated by API Evangelist tooling. Stamped 2026-08-18
# on the file's own generator header (roadmap#64). An unmarked file is
# NOT assumed to be ours -- absence of evidence was never stamped.
x-method: generated
# advance-auto-parts — Spectral ruleset (strengthened)
# Plain Spectral. Existing hand-authored rules preserved; measured rules added
# from this provider's own OpenAPI conventions by strengthen_ruleset.py,
# then self-validated against the spec.
#
# Provenance:
# - servers-https-only: 100% of servers already https (error)
# - servers-expected-domain: 2/2 servers on advanceautoparts.com
# - query-params-casing: snake @ 67% (n=27)
# - operationid-casing: camel @ 100% (n=14)
# - schema-names-casing: pascal @ 100% (n=22)
# - schema-properties-casing: snake @ 73% (n=64)
# - security: global (root) — NOT emitting operation-security-required
# - error-schema-defined: ErrorResponse
# - operation-documents-401: 86% adherence
# - pagination params observed: ['limit', 'offset']
# - merge: kept 32 existing, added 6 measured, upgraded 0
# - added: servers-expected-domain, query-params-casing, schema-names-casing, schema-properties-casing, error-schema-defined, operation-documents-401
extends:
- spectral:oas
rules:
info-title-aap-prefix:
description: API title must start with "Advance Auto Parts"
severity: warn
given: $.info.title
then:
function: pattern
functionOptions:
match: ^Advance Auto Parts
info-description-required:
description: API must have a description
severity: error
given: $.info
then:
field: description
function: truthy
info-version-required:
description: API must declare a version
severity: error
given: $.info
then:
field: version
function: truthy
info-contact-required:
description: API should include contact information
severity: warn
given: $.info
then:
field: contact
function: truthy
openapi-version-3:
description: Must use OpenAPI 3.x
severity: error
given: $
then:
field: openapi
function: pattern
functionOptions:
match: ^3\.
servers-defined:
description: API must define servers
severity: error
given: $
then:
field: servers
function: truthy
servers-https:
description: Server URLs must use HTTPS
severity: error
given: $.servers[*].url
then:
function: pattern
functionOptions:
match: ^https://
servers-description:
description: Servers should have descriptions
severity: warn
given: $.servers[*]
then:
field: description
function: truthy
paths-no-trailing-slash:
description: Paths must not have trailing slashes
severity: warn
given: $.paths[*]~
then:
function: pattern
functionOptions:
notMatch: /$
paths-lowercase-kebab:
description: Path segments should use lowercase and hyphens
severity: info
given: $.paths[*]~
then:
function: pattern
functionOptions:
match: ^/[a-z0-9{}/_-]+$
operation-summary-required:
description: Operations must have summaries
severity: error
given: $.paths[*][get,post,put,patch,delete]
then:
field: summary
function: truthy
operation-summary-aap-prefix:
description: Summaries should start with "Advance Auto Parts"
severity: warn
given: $.paths[*][get,post,put,patch,delete].summary
then:
function: pattern
functionOptions:
match: ^Advance Auto Parts
operation-description-required:
description: Operations must have descriptions
severity: error
given: $.paths[*][get,post,put,patch,delete]
then:
field: description
function: truthy
operation-id-required:
description: Operations must have operationIds
severity: error
given: $.paths[*][get,post,put,patch,delete]
then:
field: operationId
function: truthy
operation-id-camelcase:
description: operationId should use camelCase
severity: warn
given: $.paths[*][get,post,put,patch,delete].operationId
then:
function: pattern
functionOptions:
match: ^[a-z][a-zA-Z0-9]+$
operation-tags-required:
description: Operations must have tags
severity: error
given: $.paths[*][get,post,put,patch,delete]
then:
field: tags
function: truthy
parameter-description-required:
description: Parameters must have descriptions
severity: error
given: $.paths[*][*].parameters[*]
then:
field: description
function: truthy
parameter-schema-required:
description: Parameters must have schemas
severity: error
given: $.paths[*][*].parameters[*]
then:
field: schema
function: truthy
request-body-description:
description: Request bodies should have descriptions
severity: warn
given: $.paths[*][post,put,patch].requestBody
then:
field: description
function: truthy
response-success-required:
description: Operations must define 2xx responses
severity: error
given: $.paths[*][get,post,put,patch,delete]
then:
field: responses
function: schema
functionOptions:
schema:
anyOf:
- required:
- '200'
- required:
- '201'
- required:
- '204'
response-auth-defined:
description: Operations should define 401 Unauthorized response
severity: warn
given: $.paths[*][get,post,put,patch,delete].responses
then:
function: schema
functionOptions:
schema:
anyOf:
- required:
- '401'
- required:
- '400'
response-description-required:
description: Responses must have descriptions
severity: error
given: $.paths[*][*].responses[*]
then:
field: description
function: truthy
schema-description:
description: Component schemas should have descriptions
severity: warn
given: $.components.schemas[*]
then:
field: description
function: truthy
schema-type-defined:
description: Schemas should define a type
severity: warn
given: $.components.schemas[*]
then:
field: type
function: truthy
schema-properties-camelcase:
description: Schema property names should use camelCase
severity: info
given: $.components.schemas[*].properties[*]~
then:
function: pattern
functionOptions:
match: ^[a-z][a-zA-Z0-9]+$
security-schemes-defined:
description: API must define security schemes
severity: error
given: $.components
then:
field: securitySchemes
function: truthy
security-global-defined:
description: API should define global security
severity: warn
given: $
then:
field: security
function: truthy
get-no-request-body:
description: GET operations must not have request bodies
severity: error
given: $.paths[*].get
then:
field: requestBody
function: falsy
delete-returns-204:
description: DELETE operations should return 204 No Content
severity: info
given: $.paths[*].delete.responses
then:
function: schema
functionOptions:
schema:
required:
- '204'
no-empty-descriptions:
description: Descriptions must not be empty
severity: error
given: $..description
then:
function: truthy
examples-encouraged:
description: Responses should include examples
severity: info
given: $.paths[*][get,post,put,patch,delete].responses[*].content[*]
then:
function: schema
functionOptions:
schema:
anyOf:
- required:
- example
- required:
- examples
vehicle-fitment-documented:
description: Fitment endpoints should document year/make/model parameters
severity: info
given: $.paths[/vehicles*][get].parameters[*].name
then:
function: enumeration
functionOptions:
values:
- year
- makeId
- modelId
- engineId
- trim
servers-expected-domain:
description: Server URLs should be on the advanceautoparts.com domain.
severity: warn
given: $.servers[*].url
then:
function: pattern
functionOptions:
match: advanceautoparts\.com
query-params-casing:
description: Query parameters should be snake_case (the dominant convention in this API).
severity: warn
given: $.paths[*][get,post,put,patch,delete].parameters[?(@.in=='query')]
then:
field: name
function: casing
functionOptions:
type: snake
schema-names-casing:
description: Component schema names should be PascalCase (the dominant convention in this API).
severity: warn
given: $.components.schemas
then:
field: '@key'
function: casing
functionOptions:
type: pascal
schema-properties-casing:
description: Schema properties should be snake_case (the dominant convention in this API).
severity: info
given: $.components.schemas[*].properties
then:
field: '@key'
function: casing
functionOptions:
type: snake
error-schema-defined:
description: A shared error schema (ErrorResponse) should be defined for error payloads.
severity: warn
given: $.components.schemas
then:
field: ErrorResponse
function: truthy
operation-documents-401:
description: Operations should document a 401 response (documented on 86% of this API's operations).
severity: warn
given: $.paths[*][get,post,put,patch,delete].responses
then:
field: '401'
function: truthy
Every ruleset here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for spectral rules
4 MCP tools reach this
find_rulesBrowse and filter every ruleset in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.
All 92 tools →
Call it yourself
curl for this page
This ruleset
curl "https://apis.io/api/v1/rules/advance-auto-parts-spectral-rules"
All spectral rules
curl "https://apis.io/api/v1/rules?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms .
A second provider on the same verified email joins the account you already have.