oxidecomputer / oxidecomputer/omicron

Webhooks: Fetch event w/ payload and headers

Open
#8,082 0 comments 0 reactions 1 assignee View on GitHub

@hawkw is already working on this.

Since May 2, 2025.

Dominant language
Rust
Stars
572
Forks
97
Avg merge
2d 12h
Merged PRs (30d)
96

Description

It could be useful to be able to get the event payload and request headers for a delivery.

One way to do this might be to add webhook_event_fetch endpoint. Since we include the event_id but that doesn't correspond with anything the user can access. It could include the event payload, headers and list of deliveries.

This would also give us the ability to show other deliveries that correspond to the same event. For example if you have a bunch of resends, we could list them all in one place.

Alternatively we flip it and replace the webhook_delivery_list with a webhook_event_list – which includes a list of events, each containing a list of corresponding deliveries.

Note that I'm coming at this from a UX point of view, so take with a pinch of salt.

From current webhook MVP designs:
Image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.