Need more info about webhooks

Hey @Mr.Bless — the missing delivery log is the part I’d flag too. Until OpenAI ships native logging, Mark’s “log webhook deliveries yourself” workaround is basically the whole job: put a capture proxy in front of your endpoint so every delivery — headers, body, webhook-id, timestamp, and your endpoint’s response — gets recorded, then forwarded on to your real handler.

That’s what I built FlurryPORT for (disclosure: it’s mine). Point OpenAI’s webhook at the FlurryPORT capture URL and set the forward target to your actual endpoint. You get a full log of every attempt — including the 72h retries and any duplicate webhook-ids, so you can see exactly what to dedupe on — and you can replay any captured delivery against dev or prod, which partly covers the env-isolation gap since OpenAI’s scoping is project-level only. There’s a free, no-account version at flurryport.dev if you want to try it against a throwaway endpoint first.

It won’t add the pause/resume or per-API-key config you’re asking OpenAI for — those have to come from their side — but it makes deliveries visible and replayable today.