Home
Activepieces
Activepieces API Rules
Activepieces API Rules
Spectral linting rules defining API design standards and conventions for Activepieces.
31 Rules
error 10
warn 16
info 5
Generated by API Evangelist
Written by API Evangelist tooling for Activepieces's APIs. It is a starting point, not a ruleset Activepieces publishes or enforces.
Rule Categories
http
info
no
openapi
operation
pagination
parameter
path
paths
query
response
schema
security
servers
Rules
warn
info-title-format
API title should start with "Activepieces"
$.info.title
error
info-description-required
Info object must have a description
$.info
error
info-version-required
Info object must include a version
$.info
warn
openapi-version
Should use OpenAPI 3.x
$.openapi
error
servers-defined
At least one server must be defined
$
warn
servers-https
All servers should use HTTPS
$.servers[*].url
error
paths-no-trailing-slash
Paths must not have trailing slashes
$.paths[*]~
info
paths-kebab-case
Path segments should use kebab-case
$.paths[*]~
error
operation-summary-required
Every operation must have a summary
$.paths[*][get,post,put,patch,delete]
warn
operation-summary-prefix
Operation summary should start with "Activepieces"
$.paths[*][get,post,put,patch,delete].summary
warn
operation-description-required
Every operation should have a description
$.paths[*][get,post,put,patch,delete]
error
operation-operationId-required
Every operation must have an operationId
$.paths[*][get,post,put,patch,delete]
warn
operation-operationId-camelCase
OperationId should use camelCase
$.paths[*][get,post,put,patch,delete].operationId
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[*]
info
pagination-limit-param
List endpoints should support limit parameter
$.paths[*].get.parameters[*]
error
response-success-required
Every operation must have at least one 2xx response
$.paths[*][get,post,put,patch,delete].responses
error
response-description-required
Every response must have a description
$.paths[*][get,post,put,patch,delete].responses[*]
info
response-401-defined
Operations should document 401 Unauthorized response
$.paths[*][get,post,put,patch,delete].responses
error
security-schemes-defined
Security schemes must be defined
$.components
warn
security-bearer-auth
API should use Bearer authentication
$.components.securitySchemes[*]
error
http-get-no-request-body
GET operations should not have a request body
$.paths[*].get
info
http-delete-returns-204
DELETE operations should return 204
$.paths[*].delete.responses
warn
schema-description-required
Component schemas should have descriptions
$.components.schemas[*]
warn
schema-properties-have-types
Schema properties should define types
$.components.schemas[*].properties[*]
warn
servers-expected-domain
Server URLs should be on the activepieces.com domain.
$.servers[*].url
warn
path-params-casing
Path parameters should be snake_case (the dominant convention in this API).
$.paths[*].parameters[?(@.in=='path')].name
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
no-empty-descriptions
Descriptions must not be empty strings.
$..description
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
# activepieces — 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: 1/1 servers on activepieces.com
# - path-params-casing: snake @ 100% (n=13)
# - query-params-casing: snake @ 69% (n=26)
# - operationid-casing: camel @ 100% (n=27)
# - schema-names-casing: pascal @ 100% (n=25)
# - schema-properties-casing: snake @ 63% (n=103)
# - security: global (root) — NOT emitting operation-security-required
# - pagination params observed: ['cursor', 'limit']
# - merge: kept 25 existing, added 6 measured, upgraded 0
# - added: servers-expected-domain, path-params-casing, query-params-casing, schema-names-casing, schema-properties-casing, no-empty-descriptions
extends:
- spectral:oas
rules:
info-title-format:
description: API title should start with "Activepieces"
severity: warn
given: $.info.title
then:
function: pattern
functionOptions:
match: ^Activepieces
info-description-required:
description: Info object must have a description
severity: error
given: $.info
then:
field: description
function: truthy
info-version-required:
description: Info object must include a version
severity: error
given: $.info
then:
field: version
function: truthy
openapi-version:
description: Should use OpenAPI 3.x
severity: warn
given: $.openapi
then:
function: pattern
functionOptions:
match: ^3\.
servers-defined:
description: At least one server must be defined
severity: error
given: $
then:
field: servers
function: truthy
servers-https:
description: All servers should use HTTPS
severity: warn
given: $.servers[*].url
then:
function: pattern
functionOptions:
match: ^https://
paths-no-trailing-slash:
description: Paths must not have trailing slashes
severity: error
given: $.paths[*]~
then:
function: pattern
functionOptions:
notMatch: /$
paths-kebab-case:
description: Path segments should use kebab-case
severity: info
given: $.paths[*]~
then:
function: pattern
functionOptions:
notMatch: _[a-z]
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-summary-prefix:
description: Operation summary should start with "Activepieces"
severity: warn
given: $.paths[*][get,post,put,patch,delete].summary
then:
function: pattern
functionOptions:
match: '^Activepieces '
operation-description-required:
description: Every operation should have a description
severity: warn
given: $.paths[*][get,post,put,patch,delete]
then:
field: description
function: truthy
operation-operationId-required:
description: Every operation must have an operationId
severity: error
given: $.paths[*][get,post,put,patch,delete]
then:
field: operationId
function: truthy
operation-operationId-camelCase:
description: OperationId should use camelCase
severity: warn
given: $.paths[*][get,post,put,patch,delete].operationId
then:
function: casing
functionOptions:
type: camel
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
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
pagination-limit-param:
description: List endpoints should support limit parameter
severity: info
given: $.paths[*].get.parameters[*]
then:
function: schema
functionOptions:
schema:
properties:
name:
type: string
response-success-required:
description: Every operation must have 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:
- '204'
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
response-401-defined:
description: Operations should document 401 Unauthorized response
severity: info
given: $.paths[*][get,post,put,patch,delete].responses
then:
field: '401'
function: truthy
security-schemes-defined:
description: Security schemes must be defined
severity: error
given: $.components
then:
field: securitySchemes
function: truthy
security-bearer-auth:
description: API should use Bearer authentication
severity: warn
given: $.components.securitySchemes[*]
then:
function: schema
functionOptions:
schema:
properties:
scheme:
enum:
- bearer
http-get-no-request-body:
description: GET operations should not have a request body
severity: error
given: $.paths[*].get
then:
field: requestBody
function: falsy
http-delete-returns-204:
description: DELETE operations should return 204
severity: info
given: $.paths[*].delete.responses
then:
field: '204'
function: truthy
schema-description-required:
description: Component schemas should have descriptions
severity: warn
given: $.components.schemas[*]
then:
field: description
function: truthy
schema-properties-have-types:
description: Schema properties should define types
severity: warn
given: $.components.schemas[*].properties[*]
then:
field: type
function: truthy
servers-expected-domain:
description: Server URLs should be on the activepieces.com domain.
severity: warn
given: $.servers[*].url
then:
function: pattern
functionOptions:
match: activepieces\.com
path-params-casing:
description: Path parameters should be snake_case (the dominant convention in this API).
severity: warn
given: $.paths[*].parameters[?(@.in=='path')].name
then:
function: casing
functionOptions:
type: snake
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
no-empty-descriptions:
description: Descriptions must not be empty strings.
severity: warn
given: $..description
then:
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/activepieces-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.