[Devon-White]

Summary

The Fabric reference documented the call_flow and conference_room sub-resource paths in the singular, and those return 404. prime-rails config/routes.rb declares only the plural forms: resources :call_flows with nested addresses and versions, and resources :conference_rooms with nested addresses.

Changes

• Plural paths:
  • GET and POST /call_flow/{id}/versions become /call_flows/{id}/versions.
  • GET /call_flow/{id}/addresses becomes /call_flows/{id}/addresses.
  • GET /conference_room/{id}/addresses becomes /conference_rooms/{id}/addresses.
• Example pagination links now use the plural route the serializers build. The call-flow addresses example also gains the call_flows/ segment it was missing.
• Server SDK reference pages. Eight Python and TypeScript pages embedded the old endpoint strings and would have lost their schema and response snippets; only those attributes changed. The Python SDK itself still calls the singular paths, which signalwire-python#171 tracks.

Operation IDs and summaries are unchanged, so no reference URLs move. fern/redirects.yml and fern/llms.txt need no changes.

Verification

• yarn build:specs passes.
• yarn fern-md-check passes.
• Locally, yarn fern-check could only fail its missing-redirects step: Fern's server returned 403. CI should confirm.

Closes #845

[github-actions]

🌿 Preview

https://signalwire-preview-docs-857.docs.buildwithfern.com/docs

---

View workflow run

[Manny-r31]

Review verdict: Ready to merge

Checked against prime-rails main (775a2b5) config/routes.rb:1431-1443 (namespace :resources under /api/fabric): call_flows/{id}/addresses (GET), call_flows/{id}/versions (GET, POST) and conference_rooms/{id}/addresses (GET) exist only in the plural form; there is no singular route or alias. The PR head has no leftover singular paths, TypeSpec and openapi.yaml agree, all 8 SDK snippet endpoints match, and operationIds are unchanged so no redirects are needed. CI passes.

Optional follow-ups, pre-existing and outside this diff:

1. openapi.yaml ~L36274-36292: the generic ResourceAddressPaginationResponse examples use resources/{uuid}/addresses with no type segment; no such route exists.
2. openapi.yaml ~L47856: the swml_script addresses example uses singular swml_script/; the route is swml_scripts only (routes.rb:1436).

Note: the docs will be ahead of the Python SDK on these paths until signalwire-python#171 lands.

[Devon-White]

@Manny-r31 thanks for the review. Both optional follow-ups are handled:

1. Generic ResourceAddressPaginationResponse examples: no route change needed, because the generic route exists. GET /api/fabric/resources/{id}/addresses lists the addresses of any Resource, whatever its type. c346e04 updates the examples' pagination links to match the shape the API returns.
2. Singular swml_script/ in the SWML script addresses example: fixed in e9054d5. It now uses the plural swml_scripts, and there are no singular paths left in the specs or the generated OpenAPI.

Your note about the Python SDK stands: the docs will be ahead of the SDK on these paths until the SDK update lands.