Home
Apify
Apify API Rules
Apify · API Governance Rules
Apify API Rules
Spectral linting rules defining API design standards and conventions for Apify.
20 Rules
error 4
warn 14
info 2
Rule Categories
error
info
no
operation
operationid
pagination
parameter
paths
query
response
schema
security
servers
Rules
warn
info-title-prefix
API title must start with 'Apify'.
$.info
error
info-description-required
API must have a description.
$.info
error
servers-https
All server URLs must use HTTPS.
$.servers[*]
warn
operation-summary-prefix
Operation summaries must start with 'Apify'.
$.paths[*][get,post,put,patch,delete]
error
operation-id-required
Every operation must have an operationId.
$.paths[*][get,post,put,patch,delete]
warn
operation-id-camelcase
OperationId must use camelCase.
$.paths[*][get,post,put,patch,delete]
warn
operation-tags-required
Every operation must have at least one tag.
$.paths[*][get,post,put,patch,delete]
info
paths-v2-version
Paths must include API version /v2/ prefix.
$.paths
error
response-success-required
Every operation must have a 2xx response.
$.paths[*][get,post,put,patch,delete].responses
warn
parameter-description-required
All parameters must have a description.
$.paths[*][get,post,put,patch,delete].parameters[*]
info
pagination-limit-offset
Collection endpoints should use limit/offset pagination.
$.paths[*].get.parameters[*]
warn
servers-expected-domain
Server URLs should be on the apify.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
operationid-casing
Operation IDs should be camelCase (the dominant convention in this API).
$.paths[*][get,post,put,patch,delete].operationId
warn
schema-names-casing
Component schema names should be PascalCase (the dominant convention in this API).
$.components.schemas
warn
schema-properties-casing
Schema properties should be snake_case (the dominant convention in this API).
$.components.schemas[*].properties
warn
security-schemes-defined
Security schemes should be defined in components.
$.components
warn
error-schema-defined
A shared error schema (Error) should be defined for error payloads.
$.components.schemas
warn
operation-documents-401
Operations should document a 401 response (documented on 100% of this API's operations).
$.paths[*][get,post,put,patch,delete].responses
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
# apify — 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 apify.com
# - path-params-casing: camel @ 100% (n=10)
# - query-params-casing: snake @ 93% (n=15)
# - operationid-casing: camel @ 100% (n=13)
# - schema-names-casing: pascal @ 100% (n=13)
# - schema-properties-casing: snake @ 91% (n=22)
# - security: global (root) — NOT emitting operation-security-required
# - error-schema-defined: Error
# - operation-documents-401: 100% adherence
# - pagination params observed: ['limit', 'offset']
# - merge: kept 11 existing, added 9 measured, upgraded 0
# - added: servers-expected-domain, query-params-casing, operationid-casing, schema-names-casing, schema-properties-casing, security-schemes-defined, error-schema-defined, operation-documents-401, no-empty-descriptions
extends:
- spectral:oas
rules:
info-title-prefix:
description: API title must start with 'Apify'.
severity: warn
given: $.info
then:
field: title
function: pattern
functionOptions:
match: ^Apify
info-description-required:
description: API must have a description.
severity: error
given: $.info
then:
field: description
function: truthy
servers-https:
description: All server URLs must use HTTPS.
severity: error
given: $.servers[*]
then:
field: url
function: pattern
functionOptions:
match: ^https://
operation-summary-prefix:
description: Operation summaries must start with 'Apify'.
severity: warn
given: $.paths[*][get,post,put,patch,delete]
then:
field: summary
function: pattern
functionOptions:
match: ^Apify
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-id-camelcase:
description: OperationId must use camelCase.
severity: warn
given: $.paths[*][get,post,put,patch,delete]
then:
field: operationId
function: pattern
functionOptions:
match: ^[a-z][a-zA-Z0-9]*$
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
paths-v2-version:
description: Paths must include API version /v2/ prefix.
severity: info
given: $.paths
then:
field: '@key'
function: pattern
functionOptions:
notMatch: ^/v[0-9]+
response-success-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'
parameter-description-required:
description: All parameters must have a description.
severity: warn
given: $.paths[*][get,post,put,patch,delete].parameters[*]
then:
field: description
function: truthy
pagination-limit-offset:
description: Collection endpoints should use limit/offset pagination.
severity: info
given: $.paths[*].get.parameters[*]
then:
field: name
function: enumeration
functionOptions:
values:
- limit
- offset
- exclusiveStartKey
servers-expected-domain:
description: Server URLs should be on the apify.com domain.
severity: warn
given: $.servers[*].url
then:
function: pattern
functionOptions:
match: apify\.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
operationid-casing:
description: Operation IDs should be camelCase (the dominant convention in this API).
severity: warn
given: $.paths[*][get,post,put,patch,delete].operationId
then:
function: casing
functionOptions:
type: camel
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: warn
given: $.components.schemas[*].properties
then:
field: '@key'
function: casing
functionOptions:
type: snake
security-schemes-defined:
description: Security schemes should be defined in components.
severity: warn
given: $.components
then:
field: securitySchemes
function: truthy
error-schema-defined:
description: A shared error schema (Error) should be defined for error payloads.
severity: warn
given: $.components.schemas
then:
field: Error
function: truthy
operation-documents-401:
description: Operations should document a 401 response (documented on 100% of this API's operations).
severity: warn
given: $.paths[*][get,post,put,patch,delete].responses
then:
field: '401'
function: truthy
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/apify-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.