Skip to content

20608 - Compatibility API: clarify StatusCallbackEvent surfaces terminal failed events - #631

Open
Mikeysax wants to merge 1 commit into
mainfrom
mikeysax/20608/status-callback-event-docs
Open

20608 - Compatibility API: clarify StatusCallbackEvent surfaces terminal failed events#631
Mikeysax wants to merge 1 commit into
mainfrom
mikeysax/20608/status-callback-event-docs

Conversation

@Mikeysax

@Mikeysax Mikeysax commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

What

Updates the OpenAPI description of the StatusCallbackEvent parameter for the Calls API to document the new behavior from prime-rails#9876 (cloud-product#20528):

Subscribing to completed now also surfaces a final status: failed webhook when the call is blocked by:

  • the Musubi call-scoring service (with ErrorCode 20429)
  • the Do Not Originate registry
  • an empty endpoint list
  • a temporary infrastructure error

The new callbacks are additive — no action is required for existing integrations. Documentation-only change; no schema impact.

Diff

fern/apis/compatibility/openapi.yaml — single-line update to the StatusCallbackEvent parameter description. One sentence appended clarifying the new behavior.

Why

Per CONTRIBUTING.md and the rollout runbook on cloud-product#20400, customer-facing behavior changes require public API docs updates before merge. PR #9876 introduces this new callback behavior; the OpenAPI spec currently doesn't reflect it.

Cross-references

Review focus

  • Voice-product owner: does the one-sentence addition read naturally alongside the existing parameter description? Is the wording clear enough that a customer reading the OpenAPI spec can predict the new behavior without consulting release notes?
  • Public docs team (Isa Meyer): is the wording consistent with the rest of the voice/LaML docs page (e.g., fern/products/compatibility-api/pages/cxml/voice/ MDX content)? If MDX content also needs updating, file a follow-up.

Deploy notes

  • This is a docs-only change. Public API docs auto-regenerate from the OpenAPI spec on merge to main.
  • The note about "no action required for existing integrations" should be confirmed against the public changelog entry before merge — the two should agree on the framing.
  • After this PR merges, the customer-facing changelog entry (workstream 3 of #20608) is the last remaining artifact before PR #9876 can merge.

Ready for review — reviewers requested

Per CONTRIBUTING.md this is one of the gating artifacts for merging prime-rails#9876. The wording is grounded in shipped code; iterate freely in review. The customer-facing changelog entry (workstream 3 of #20608) should align with this wording — but the changelog lives in the release-notes channel and can be tweaked at any point, so no need to gate this PR on it.

… failed events

Updates the description of the StatusCallbackEvent parameter for the
Calls API to document the new behavior from prime-rails#9876 (cloud-product#20528):
subscribing to completed now also surfaces a final status: failed webhook
when the call is blocked by Musubi (with ErrorCode 20429), the DNO registry,
no-registered-endpoints, or a temporary error. The new callbacks are additive;
no action is required for existing integrations.

Refs cloud-product#20608 (workstream 1, public API docs).
Refs cloud-product#20528 (the underlying behavior gap).
Refs prime-rails#9876 (the code PR).
@Mikeysax
Mikeysax marked this pull request as ready for review August 25, 2026 16:13
@Mikeysax
Mikeysax requested a review from meyerisabela August 25, 2026 16:13
@Mikeysax Mikeysax self-assigned this Aug 25, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant