Threads · API Governance Rules

Threads API Rules

Spectral linting rules defining API design standards and conventions for Threads.

7 Rules error 3 warn 3 info 1
View Rules File View on GitHub

Rule Categories

threads

Rules

warn
threads-api-operation-summary-title-case
All operation summaries must use Title Case.
$.paths[*][*].summary
error
threads-api-oauth2-required
Operations must use OAuth2 security scheme.
$.components.securitySchemes
error
threads-api-tag-defined
All operations must have at least one tag.
$.paths[*][get,post,put,delete]
info
threads-api-me-prefix-paths
User-specific endpoints should use /me prefix pattern.
$.paths
warn
threads-api-fields-query-param
GET operations retrieving media objects should support fields parameter.
$.paths[*][get].parameters[*]
error
threads-api-response-defined
All operations must define at least one response.
$.paths[*][*]
warn
threads-api-operation-id-camel-case
Operation IDs should use camelCase.
$.paths[*][*].operationId

Spectral Ruleset

Raw ↑
extends: spectral:oas
rules:
  # Threads API (Meta) specific Spectral rules

  threads-api-operation-summary-title-case:
    description: All operation summaries must use Title Case.
    message: "Operation summary '{{value}}' should use Title Case."
    severity: warn
    given: "$.paths[*][*].summary"
    then:
      function: pattern
      functionOptions:
        match: "^([A-Z][a-z0-9]*([ -][A-Z0-9][a-z0-9]*)*)$"

  threads-api-oauth2-required:
    description: Operations must use OAuth2 security scheme.
    message: "Threads API operations require OAuth2 authentication."
    severity: error
    given: "$.components.securitySchemes"
    then:
      field: oauth2Auth
      function: truthy

  threads-api-tag-defined:
    description: All operations must have at least one tag.
    message: "Operations must have at least one tag for categorization."
    severity: error
    given: "$.paths[*][get,post,put,delete]"
    then:
      field: tags
      function: truthy

  threads-api-me-prefix-paths:
    description: User-specific endpoints should use /me prefix pattern.
    message: "User-specific Threads endpoints should use /me/ path prefix."
    severity: info
    given: "$.paths"
    then:
      function: truthy

  threads-api-fields-query-param:
    description: GET operations retrieving media objects should support fields parameter.
    message: "Threads API GET operations should support fields query parameter for selective field retrieval."
    severity: warn
    given: "$.paths[*][get].parameters[*]"
    then:
      function: truthy

  threads-api-response-defined:
    description: All operations must define at least one response.
    message: "Operations must define response schemas."
    severity: error
    given: "$.paths[*][*]"
    then:
      field: responses
      function: truthy

  threads-api-operation-id-camel-case:
    description: Operation IDs should use camelCase.
    message: "Operation ID '{{value}}' should use camelCase."
    severity: warn
    given: "$.paths[*][*].operationId"
    then:
      function: pattern
      functionOptions:
        match: "^[a-z][a-zA-Z0-9]*$"

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/threads-api-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 email required.

A second provider on the same verified email joins the account you already have.