Help
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Pilot Lvl 1
Message 1 of 3

[FR] No way to match delivered events with ones queried via API

Delivering webhooks to GitHub Apps may be unreliable given the nature of the Internet they are like UDP: no delivery guarantee.

 

To solve this, I'm looking at having an event stream on the Application side.

 

The idea is to put any incoming events to the storage and then time to time query GitHub API to get a list of the recent events. Then, try to match those with ones stored on the App side. Finally, process events found missing locally.

 

I'm trying out endpoints like https://api.github.com/orgs/ansible/events, https://api.github.com/repos/webknjaz/ansible-gentoo-lap....

They seem to have payloads but there are no unique identifiers like on the recent deliveries page (e.g. https://github.com/settings/apps/ansiwatch/advanced) which have X-GitHub-Delivery listed there.

 

The idea (request?) is to have those IDs accessible via API as well. It seems like API exposes a numeric ID while UI exposes delivery ID. And I cannot compare 8884215857 == fbde0650-1821-11e9-8b32-053f039e511a which is unfortunate.

 

Any chance you could add a numeric event ID to webhook events? Or add a delivery ID to responses available via Events API? Or both?

2 Replies
Community Manager
Message 2 of 3

Re: [FR] No way to match delivered events with ones queried via API

Thanks for taking the time to write this feedback! I've taken your suggestion and passed it along to the appropriate teams. Thanks again for reaching out 😀


Best,
AndreaG

Mark helpful posts with Accept as Solution to help other users locate important info. Don't forget to give Kudos for great content!

Copilot Lvl 2
Message 3 of 3

Re: [FR] No way to match delivered events with ones queried via API


@AndreaGriffiths11 wrote:

Thanks for taking the time to write this feedback! I've taken your suggestion and passed it along to the appropriate teams. Thanks again for reaching out 😀



@AndreaGriffiths11 wrote:

Thanks for taking the time to write this feedback! I've taken your suggestion and passed it along to the appropriate teams. Thanks again for reaching out 😀