Apple Pay · API Governance Rules

Apple Pay API Rules

Spectral linting rules defining API design standards and conventions for Apple Pay.

24 Rules error 10 warn 12 info 2
View Rules File View on GitHub

Rule Categories

external http info no operation parameter paths response schema security servers

Rules

warn
info-title-apple-prefix
API title should start with "Apple Pay"
$.info
error
info-version-required
API version must be specified
$.info
warn
info-description-required
API description must be present
$.info
info
info-contact-required
Contact information should be provided
$.info
warn
info-terms-of-service
Terms of service URL should be provided for payment APIs
$.info
error
servers-required
At least one server must be defined
$
error
servers-https
Server URLs must use HTTPS for payment APIs
$.servers[*]
warn
servers-description-required
Each server must have a description distinguishing production from sandbox
$.servers[*]
error
security-defined
Global security scheme must be defined for payment APIs
$
error
security-schemes-defined
Security schemes must be defined in components
$.components
warn
paths-kebab-case
Path segments must use camelCase or kebab-case
$.paths
error
operation-summary-required
Every operation must have a summary
$.paths[*][get,post,put,patch,delete]
error
operation-id-required
Every operation must have an operationId
$.paths[*][get,post,put,patch,delete]
warn
operation-description-required
Every operation must have a description
$.paths[*][get,post,put,patch,delete]
warn
operation-tags-required
Every operation must have at least one tag
$.paths[*][get,post,put,patch,delete]
warn
parameter-description-required
Every parameter must have a description
$.paths[*][get,post,put,patch,delete].parameters[*]
error
operation-success-response-required
Every operation must have a 2xx response
$.paths[*][get,post,put,patch,delete].responses
warn
response-401-for-payment-apis
Payment APIs must define 401 Unauthorized responses
$.paths[*][post].responses
error
response-description-required
Every response must have a description
$.paths[*][get,post,put,patch,delete].responses[*]
warn
schema-title-required
Component schemas must have a title
$.components.schemas[*]
warn
schema-description-required
Component schemas should have a description
$.components.schemas[*]
error
http-get-no-request-body
GET operations must not have a request body
$.paths[*].get
warn
no-empty-descriptions
Descriptions must not be empty
$..description
info
external-docs-encouraged
External documentation links are encouraged for payment APIs
$

Spectral Ruleset

Raw ↑ 
rules:

  # INFO / METADATA
  info-title-apple-prefix:
    description: API title should start with "Apple Pay"
    severity: warn
    given: $.info
    then:
      field: title
      function: pattern
      functionOptions:
        match: "^Apple Pay"

  info-version-required:
    description: API version must be specified
    severity: error
    given: $.info
    then:
      field: version
      function: truthy

  info-description-required:
    description: API description must be present
    severity: warn
    given: $.info
    then:
      field: description
      function: minLength
      functionOptions:
        min: 20

  info-contact-required:
    description: Contact information should be provided
    severity: info
    given: $.info
    then:
      field: contact
      function: truthy

  info-terms-of-service:
    description: Terms of service URL should be provided for payment APIs
    severity: warn
    given: $.info
    then:
      field: termsOfService
      function: truthy

  # SERVERS
  servers-required:
    description: At least one server must be defined
    severity: error
    given: $
    then:
      field: servers
      function: truthy

  servers-https:
    description: Server URLs must use HTTPS for payment APIs
    severity: error
    given: $.servers[*]
    then:
      field: url
      function: pattern
      functionOptions:
        match: "^https://"

  servers-description-required:
    description: Each server must have a description distinguishing production from sandbox
    severity: warn
    given: $.servers[*]
    then:
      field: description
      function: truthy

  # SECURITY
  security-defined:
    description: Global security scheme must be defined for payment APIs
    severity: error
    given: $
    then:
      field: security
      function: truthy

  security-schemes-defined:
    description: Security schemes must be defined in components
    severity: error
    given: $.components
    then:
      field: securitySchemes
      function: truthy

  # PATHS — NAMING
  paths-kebab-case:
    description: Path segments must use camelCase or kebab-case
    severity: warn
    given: $.paths
    then:
      field: "@key"
      function: pattern
      functionOptions:
        match: "^(/[a-zA-Z0-9{}/_-]+)+$"

  # OPERATIONS
  operation-summary-required:
    description: Every operation must have a summary
    severity: error
    given: $.paths[*][get,post,put,patch,delete]
    then:
      field: summary
      function: truthy

  operation-id-required:
    description: Every operation must have an operationId
    severity: error
    given: $.paths[*][get,post,put,patch,delete]
    then:
      field: operationId
      function: truthy

  operation-description-required:
    description: Every operation must have a description
    severity: warn
    given: $.paths[*][get,post,put,patch,delete]
    then:
      field: description
      function: truthy

  operation-tags-required:
    description: Every operation must have at least one tag
    severity: warn
    given: $.paths[*][get,post,put,patch,delete]
    then:
      field: tags
      function: truthy

  # PARAMETERS
  parameter-description-required:
    description: Every parameter must have a description
    severity: warn
    given: $.paths[*][get,post,put,patch,delete].parameters[*]
    then:
      field: description
      function: truthy

  # RESPONSES
  operation-success-response-required:
    description: Every operation must have a 2xx response
    severity: error
    given: $.paths[*][get,post,put,patch,delete].responses
    then:
      function: schema
      functionOptions:
        schema:
          anyOf:
            - required: ['200']
            - required: ['201']
            - required: ['204']

  response-401-for-payment-apis:
    description: Payment APIs must define 401 Unauthorized responses
    severity: warn
    given: $.paths[*][post].responses
    then:
      field: '401'
      function: truthy

  response-description-required:
    description: Every response must have a description
    severity: error
    given: $.paths[*][get,post,put,patch,delete].responses[*]
    then:
      field: description
      function: truthy

  # SCHEMAS
  schema-title-required:
    description: Component schemas must have a title
    severity: warn
    given: $.components.schemas[*]
    then:
      field: title
      function: truthy

  schema-description-required:
    description: Component schemas should have a description
    severity: warn
    given: $.components.schemas[*]
    then:
      field: description
      function: truthy

  # HTTP METHOD CONVENTIONS
  http-get-no-request-body:
    description: GET operations must not have a request body
    severity: error
    given: $.paths[*].get
    then:
      field: requestBody
      function: falsy

  # GENERAL QUALITY
  no-empty-descriptions:
    description: Descriptions must not be empty
    severity: warn
    given: $..description
    then:
      function: pattern
      functionOptions:
        match: ".+"

  external-docs-encouraged:
    description: External documentation links are encouraged for payment APIs
    severity: info
    given: $
    then:
      field: externalDocs
      function: truthy