Skip to main content

​
Changelog

​
OpenAPI accuracy from Rails controllers
  • Rebuilt auto-synced operations from controller strong params, query params, and render_* / head statuses.
  • Knowledge bases, follow-ups, DNC, models, and prompt-overage now document real request fields instead of additionalProperties: true stubs.
  • Plivo answer/AMD no longer advertise Callaro 401s; they document vendor signature 403 / 503 and XML/JSON 200s.
  • Added 401/403 to handwritten tenant list/show operations that only documented 200.
  • Retagged GET /effective_conversation_mode from Platform to Models so it publishes on the public spec.
​
OpenAPI route coverage sync
  • Reconciled voice_saas_api/docs/openapi.yaml against live Rails /api/v1 routes (647 operations).
  • Published missing tenant families: knowledge bases, models, follow-ups, DNC, custom fields, campaign templates, call analysis, MCP servers, and prompt addendums.
  • Corrected telephony webhook auth: vendor signature/token only, not Callaro API keys. Documented GET plus 202/403/404/422/500 outcomes.
​
Standalone docs pipeline and product coverage
  • Moved callaro-docs to a standalone repository with sibling-repo OpenAPI resolution and a vendored source snapshot for CI.
  • Added npm run docs:pipeline to regenerate OpenAPI, Postman, assets, and QA gates from ai_calling/.
  • Documented Plivo BYOT telephony and knowledge-base publish/link workflows.
  • Marked knowledge-base and models families as live-but-not-generated in OpenAPI coverage status.
​
Initial public docs
Published the first complete Callaro developer docs structure covering onboarding, concepts, API guides, integrations, partners, trust, and the help center source in user-guides/.
​
Contract and docs governance hardening
  • Corrected contacts/import request contract to multipart upload flows.
  • Normalized cursor pagination examples to cursor + page_size with data.next_cursor.
  • Added telephony vendor webhook ingress endpoints to source and generated API references.
  • Added Postman generation pipeline and QA gates for nav drift, related-article links, asset status taxonomy, and critical contract checks.

​
Changelog policy

  • Record endpoint-level changes that affect request/response shape, auth, pagination, or error behavior.
  • Record workflow-level changes (for example campaign launch flow, webhook handling, export reconciliation).
  • Include migration notes when behavior changes can affect existing integrations.