Telstra · API Governance Rules
Telstra API Rules
Spectral linting rules defining API design standards and conventions for Telstra.
5 Rules
error 2
warn 3
Rule Categories
telstra
Rules
warn
telstra-operation-summary-title-case
Operation summaries should be in Title Case and prefixed with "Telstra ".
$.paths.*[get,post,put,delete,patch].summary
error
telstra-bearer-or-oauth-only
Every operation must use OAuth2ClientCredentials with the NSMS or MNV scope, except the token endpoint.
$.paths[?(@property != '/oauth/token')]..security[*]
warn
telstra-error-response-shape
4xx and 5xx responses should reference the canonical ErrorResponse schema.
$.paths.*.*.responses.[4??,5??].content.application/json.schema
error
telstra-host-must-be-tapi
Server URL must use tapi.telstra.com.
$.servers[*].url
warn
telstra-info-contact
Spec must include Telstra Developer support contact.
$.info.contact
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/telstra-rules"
All spectral rules
curl "https://apis.io/api/v1/rules?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.