Send Webhook Object on Webhooks Update Event

[APixelVisuals]

The webhooks update event provides a guild ID and channel ID, but doesn't tell you which webhook was updated. It also doesn't specify if it's possible for multiple webhooks to be updated at once.

This data can be found if your application caches webhooks by fetching the channel's webhooks and comparing the data, but that would require an extra API call, using up the rate limit bucket. Other update events, such as guild/channel/role update events provide the updated data, so I'm not sure why the same can't be done for webhooks.

I think that the event should include the update type (created, updated, or deleted), and the webhook object if the update type is created or updated.

The same can be improved for the guild integrations update event.

[jhgg]

The reason for this (and the guild integrations update event) is really for the client to reload the webhooks/integrations in the UI. We did this somewhat as a quick hack to simplify the protocol.

It would be interesting to know under what circumstances this information is relevant to bots. I don't think that a bot should attempt to maintain a mapping of active webhooks. We do not send this info in GUILD_CREATE for example, so it isn't really state that a bot could start out with that needs to be actively updated.

[muddyfish]

My bot caches a full list of webhooks in a guild, because it needs to use webhook specific features (custom username/avatar, emojis from servers bot isn't in).

My current solution is to download a full list when I don't have any, and then use that until one of my webhooks has moved or gets deleted, and then downloading the list again. This generally means you don't need continuous updates, except for the case when a user moves a webhook and you can't know where it is until you post a message through it (or download the full list again through the get webhooks endpoint)

[APixelVisuals]

My bot needs to keep track of it's own webhooks and check for them getting deleted

[jhgg]

My bot needs to keep track of it's own webhooks and check for them getting deleted

You'll know when the webhook is deleted when you try and invoke it though. That's the intended use of the API.

[jhgg]

This generally means you don't need continuous updates, except for the case when a user moves a webhook and you can't know where it is until you post a message through it (or download the full list again through the get webhooks endpoint)

Either way you would miss these events when the bot is offline anyways, and you have no real means to sync webhooks without re-fetching them all...