convoy
convoy copied to clipboard
The Cloud Native Webhooks Gateway
**Problem Description** Most API providers have two environments: `development` and `live`. For these two environments, users are expected to create two separate webhook endpoints. Today, Convoy users either create two...
Currently, the flow to ingest webhook events in an incoming project is to 1. Create a Source 2. Retrieve the Source URL. 3. Add Source URL to your Providers webhooks...
Basically, we can help users start debugging events from anywhere, including the event trigger response. We can make an API response on triggering an event to source a little prettier...
We should implement a technique to validate that the endpoint owner controls the endpoint. Similar implementations in the wild are as follows: - [Twitter](https://developer.twitter.com/en/docs/twitter-api/enterprise/account-activity-api/guides/securing-webhooks) - [Okta](https://developer.okta.com/docs/concepts/event-hooks/#one-time-verification-request)
Rewrite our authorisation system using the open policy agent.
**Problem Description** Aggregate Webhooks Payload from multiple sources.
I would like to support Convoy by implementing [Uffizzi](https://github.com/UffizziCloud/uffizzi) preview environments. Disclaimer: I work on [Uffizzi](https://github.com/UffizziCloud/uffizzi). Uffizzi is a Open Source full stack previews engine and our platform is available...