Planable · OpenAPI Overlay 1.0.0

API Evangelist enhancements — Planable Social Listening API

8 actions 8 updates documentation extends openapi/planable-social-listening-api-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for Planable's API. It is a proposal applied on top of the contract, not a document Planable publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

operationIdx-rate-limitsx-error-catalogx-conventionsx-idempotencyx-plan-gatex-docs

Targets 8

$.paths['/keywords'].get
$.paths['/keywords'].post
$.paths['/keywords/{keywordId}'].delete
$.paths['/keywords/{keywordId}/mentions'].get
$.paths['/keywords/{keywordId}/metrics/summary'].get
$.paths['/keywords/{keywordId}/metrics'].get
$.paths['/keywords/{keywordId}/sync-status'].get
$.info

OpenAPI Overlay

Raw ↑ 
overlay: 1.0.0
info:
  title: API Evangelist enhancements — Planable Social Listening API
  version: 1.0.0
extends: openapi/planable-social-listening-api-openapi.yml
x-generated: '2026-08-13'
x-method: generated
x-source: openapi/_original/planable-openapi.json
x-note: Non-destructive enhancement of Planable's published contract. Planable declares no operationId on any of
  its 51 operations, which forces every generator and MCP tool-forge to synthesize names. This overlay assigns deterministic
  verb+path operationIds and documents the runtime semantics Planable states in prose but does not encode in the
  spec. The operationIds are API EVANGELIST's, not Planable's — do not cite them as published. The original spec
  is never mutated.
actions:
- target: $.paths['/keywords'].get
  description: Assign a stable operationId for GET /keywords — the published spec declares none.
  update:
    operationId: getKeywords
- target: $.paths['/keywords'].post
  description: Assign a stable operationId for POST /keywords — the published spec declares none.
  update:
    operationId: createKeywords
- target: $.paths['/keywords/{keywordId}'].delete
  description: Assign a stable operationId for DELETE /keywords/{keywordId} — the published spec declares none.
  update:
    operationId: deleteKeywordsByKeywordId
- target: $.paths['/keywords/{keywordId}/mentions'].get
  description: Assign a stable operationId for GET /keywords/{keywordId}/mentions — the published spec declares
    none.
  update:
    operationId: getKeywordsByKeywordIdMentions
- target: $.paths['/keywords/{keywordId}/metrics/summary'].get
  description: Assign a stable operationId for GET /keywords/{keywordId}/metrics/summary — the published spec declares
    none.
  update:
    operationId: getKeywordsByKeywordIdMetricsSummary
- target: $.paths['/keywords/{keywordId}/metrics'].get
  description: Assign a stable operationId for GET /keywords/{keywordId}/metrics — the published spec declares none.
  update:
    operationId: getKeywordsByKeywordIdMetrics
- target: $.paths['/keywords/{keywordId}/sync-status'].get
  description: Assign a stable operationId for GET /keywords/{keywordId}/sync-status — the published spec declares
    none.
  update:
    operationId: getKeywordsByKeywordIdSyncStatus
- target: $.info
  description: Record the runtime semantics Planable publishes in its developer guide but omits from the spec.
  update:
    x-rate-limits:
      read: 600 requests/minute per token
      write: 120 requests/minute per token
      algorithm: Redis-backed sliding window
      headers:
      - X-RateLimit-Limit
      - X-RateLimit-Remaining
      - X-RateLimit-Reset
      retry_after: false
      source: https://planable.io/guides/planable-public-api/
    x-error-catalog: errors/planable-problem-types.yml
    x-conventions: conventions/planable-conventions.yml
    x-idempotency:
      header: null
      mechanism: natural-key semantic idempotency on 4 operations
      detail: conventions/planable-conventions.yml
    x-plan-gate: API token generation requires a Pro or Enterprise plan
    x-docs: https://api.planable.io/api/v1/docs