UPS · API Governance Rules
UPS API Rules
Spectral linting rules defining API design standards and conventions for UPS.
6 Rules
warn 3
info 3
Rule Categories
ups
Rules
warn
ups-operation-ids-camel-case
Operation IDs must use camelCase
$.paths[*][*].operationId
warn
ups-summaries-title-case
Operation summaries must use Title Case
$.paths[*][*].summary
warn
ups-bearer-auth-required
All non-OAuth operations must use BearerAuth
$.paths[?(!@property.match(/\/oauth\/token/))][get,post,delete]
info
ups-request-wrappers
UPS API requests use PascalCase wrapper objects
$.paths[*][post,put].requestBody.content.application/json.schema
info
ups-void-uses-delete
Void/cancel operations should use DELETE method
$.paths[?(@property.match(/void|cancel/))]
info
ups-tracking-number-path-param
Tracking endpoints use path parameters for tracking numbers
$.paths[?(@property.match(/track/))]
Spectral Ruleset
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.
Call it yourself
curl for this page
This ruleset
curl "https://apis.io/api/v1/rules/ups-rules"
All spectral rules
curl "https://apis.io/api/v1/rules?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.