Rewrite: Webhooks

[Manny-r31]

Rewrite of Webhooks pages to match how to correctly setup webhooks in current dashboard

Description

Rewrite of Webhooks pages to match how to correctly setup webhooks in current dashboard. Old webhooks page referenced legacy dashboard and was not formatted properly. Also had a lot of redundancy.

Type of Change

• Documentation update

Related Issues

#370

Testing

• Tested manually

Checklist

• I have read the CONTRIBUTING guidelines
• My code follows the project's style guidelines
• I have updated documentation (if applicable)
• All existing tests pass

[github-actions]

🌿 Preview

https://signalwire-preview-09df34b3-28ea-4afe-bd1f-f2ab52a1d70a.docs.buildwithfern.com/docs

---

View workflow run

[hey-august]

LGTM!

[hey-august]

Voice-calls row may under-specify what's required to receive these states.

The status-callback table lists call_state_url on connect as the thing to set, with "States you'll receive: created, ringing, answered, ended." But delivering those states actually takes a second parameter, call_state_events, which selects which states are sent — and per the spec it defaults to ['ended']:

// specs/swml/calling/Methods/connect/main.tsp:171
call_state_events?: CallStatus[] = #[CallStatus.ended];

So a reader who sets only call_state_url will receive just ended, not the four states the table promises. Messages and Recordings don't have this opt-in array, so those rows are correct as written — voice is the only one with the two-parameter shape, which is what makes it easy to miss.

Suggest a short note under the table rather than widening the column:

<Note>
For voice calls, `call_state_events` defaults to `['ended']` — set it explicitly to also receive `created`, `ringing`, and `answered`.
</Note>

[hey-august]

LEBNTM! (looks even better now to me)