[GG-1303] Fix webhook API docs to match how the server behaves

[tayjohno]

Problem

GG-1303 flagged places where the webhook docs don't match what the API actually does. If you follow the docs as written, you get a 415 or a webhook that never fires.

Change

Docs said	API actually does	Fix
A new webhook gets every event by default	Sends only the events you list, and none if you list nothing (test)	events stays optional, but now says it sends nothing when omitted and that unknown event names return a 422
The create-webhook curl example works as written	Rejects non-JSON create/update requests with a 415 (v2 and v3 base controllers)	Added the JSON Content-Type header to the three body examples that lacked it: webhook create, plus workflow trigger create and update
Use include_received_email to get received-email events	Still accepted, but adding subscriber.received_email to events does the same thing	Kept the argument and marked it deprecated. It stays in both response examples, and the properties table explains it's read-only and derived from events
Received-email notifications are "optional"	Every event is optional, so the note says nothing useful	Swapped in the ticket's wording (very high volume, only use it if you need it) and linked to Setting Up

Setting Up rewrite. The section now walks through the real UI: Webhooks settings, "New webhook", URL, "All Events" or "Select Events", "Save". It also warns that "All Events" includes the high-volume received-email event. Every label was checked against the drip views.

Example fixes.

• version is now an integer, matching the column type.
• Dropped trailing commas in the links objects and added two missing commas in the event payload examples. Every JSON example on these pages now parses, except two that use comment placeholders on purpose.
• Response key order now matches what the API returns.
• Fixed a few typos.

The Ruby example still passes false for the deprecated flag because the gem's signature requires that argument. A one-line comment points readers to the events list instead.

Testing

• Parsed every JSON example with a script. The Ruby snippets pass ruby -c.
• Scanned every shell example for a request body without a Content-Type header. None left.
• Not done: a local Middleman build, because the gems aren't installed here. The change is plain markdown and table rows, but CI or a preview should confirm it renders.

Open questions

• Webhooks set to "All Events" in the UI get received-email events but report the deprecated flag as false. The docs now say so. Is that worth fixing in drip, or is a docs note enough?

🤖 Generated with Claude Code