Azure Logic Apps · API Governance Rules

Azure Logic Apps API Rules

Spectral linting rules defining API design standards and conventions for Azure Logic Apps.

18 Rules error 5 warn 9 info 4
Generated by API Evangelist Written by API Evangelist tooling for Azure Logic Apps's APIs. It is a starting point, not a ruleset Azure Logic Apps publishes or enforces.
View Rules File View on GitHub

Rule Categories

info no openapi operation parameter path paths query response schema security servers tags

Rules

warn
info-title-format
API title must start with "Azure Logic Apps"
$.info.title
warn
operation-summary-prefix
Operation summaries must start with "Azure Logic Apps"
$.paths[*][get,post,put,patch,delete].summary
error
operation-id-required
All operations must have an operationId
$.paths[*][get,post,put,patch,delete]
error
operation-summary-required
All operations must have a summary
$.paths[*][get,post,put,patch,delete]
warn
operation-description-required
All operations must have a description
$.paths[*][get,post,put,patch,delete]
warn
operation-tags-required
All operations must have at least one tag
$.paths[*][get,post,put,patch,delete]
error
paths-no-trailing-slash
Paths must not end with a trailing slash
$.paths[*]~
warn
openapi-version
Must use OpenAPI 3.x or Swagger 2.x
$
error
servers-https
All server URLs must use HTTPS
$.servers[*].url
error
response-success-required
Operations must define at least one 2xx response
$.paths[*][get,post,put,patch,delete].responses
warn
parameter-description-required
All inline parameters must have descriptions
$.paths[*][get,post,put,patch,delete].parameters[?(!@.$ref)]
info
schema-properties-description
Top-level schema properties should have descriptions
$.components.schemas[*].properties[*]
info
tags-global-definition
All tags used in operations should be defined globally
$.tags
info
operation-id-camel-case
OperationIds should use consistent naming
$.paths[*][get,post,put,patch,delete].operationId
info
security-defined
Security schemes should be defined
$.components.securitySchemes
warn
path-params-casing
Path parameters should be camelCase (the dominant convention in this API).
$.paths[*].parameters[?(@.in=='path')].name
warn
query-params-casing
Query parameters should be kebab-case (the dominant convention in this API).
$.paths[*][get,post,put,patch,delete].parameters[?(@.in=='query')]
warn
no-empty-descriptions
Descriptions must not be empty strings.
$..description

Spectral Ruleset

Raw ↑
# 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
# azure-logic-apps — 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:
#   - path-params-casing: camel @ 100% (n=388)
#   - query-params-casing: kebab @ 79% (n=134)
#   - merge: kept 15 existing, added 3 measured, upgraded 0
#   - added: path-params-casing, query-params-casing, no-empty-descriptions
extends:
  - spectral:oas
rules:
  info-title-format:
    description: API title must start with "Azure Logic Apps"
    severity: warn
    given: $.info.title
    then:
      function: pattern
      functionOptions:
        match: ^Azure
  operation-summary-prefix:
    description: Operation summaries must start with "Azure Logic Apps"
    severity: warn
    given: $.paths[*][get,post,put,patch,delete].summary
    then:
      function: pattern
      functionOptions:
        match: ^Azure
  operation-id-required:
    description: All operations must have an operationId
    severity: error
    given: $.paths[*][get,post,put,patch,delete]
    then:
      field: operationId
      function: truthy
  operation-summary-required:
    description: All operations must have a summary
    severity: error
    given: $.paths[*][get,post,put,patch,delete]
    then:
      field: summary
      function: truthy
  operation-description-required:
    description: All operations must have a description
    severity: warn
    given: $.paths[*][get,post,put,patch,delete]
    then:
      field: description
      function: truthy
  operation-tags-required:
    description: All operations must have at least one tag
    severity: warn
    given: $.paths[*][get,post,put,patch,delete]
    then:
      field: tags
      function: truthy
  paths-no-trailing-slash:
    description: Paths must not end with a trailing slash
    severity: error
    given: $.paths[*]~
    then:
      function: pattern
      functionOptions:
        notMatch: /$
  openapi-version:
    description: Must use OpenAPI 3.x or Swagger 2.x
    severity: warn
    given: $
    then:
      function: truthy
  servers-https:
    description: All server URLs must use HTTPS
    severity: error
    given: $.servers[*].url
    then:
      function: pattern
      functionOptions:
        match: ^https://
  response-success-required:
    description: Operations must define at least one 2xx response
    severity: error
    given: $.paths[*][get,post,put,patch,delete].responses
    then:
      function: schema
      functionOptions:
        schema:
          anyOf:
          - required:
            - '200'
          - required:
            - '201'
          - required:
            - '202'
          - required:
            - '204'
  parameter-description-required:
    description: All inline parameters must have descriptions
    severity: warn
    given: $.paths[*][get,post,put,patch,delete].parameters[?(!@.$ref)]
    then:
      field: description
      function: truthy
  schema-properties-description:
    description: Top-level schema properties should have descriptions
    severity: info
    given: $.components.schemas[*].properties[*]
    then:
      field: description
      function: truthy
  tags-global-definition:
    description: All tags used in operations should be defined globally
    severity: info
    given: $.tags
    then:
      function: truthy
  operation-id-camel-case:
    description: OperationIds should use consistent naming
    severity: info
    given: $.paths[*][get,post,put,patch,delete].operationId
    then:
      function: truthy
  security-defined:
    description: Security schemes should be defined
    severity: info
    given: $.components.securitySchemes
    then:
      function: truthy
  path-params-casing:
    description: Path parameters should be camelCase (the dominant convention in this API).
    severity: warn
    given: $.paths[*].parameters[?(@.in=='path')].name
    then:
      function: casing
      functionOptions:
        type: camel
  query-params-casing:
    description: Query parameters should be kebab-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: kebab
  no-empty-descriptions:
    description: Descriptions must not be empty strings.
    severity: warn
    given: $..description
    then:
      function: truthy

Work with this as data

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/azure-logic-apps-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.