You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to contribute to the API by implementing a webhook system that can notify subscribed apps that an update to the database has happened, instead of requiring apps to make request after request to check if the API has been updated. Not all apps would benefit from this, but if there are any apps that only need data when an update has occurred, a webhook system is far more efficient.
Let me know if you would like my contribution on this
The text was updated successfully, but these errors were encountered:
This is something I'd consider after we've run through a few rounds of data imports to ensure our processes are ironed out.
Could you expand a bit more on some details of your proposal?
For example, what sort of use case this will be useful for and how it'd make working with the API better for consumers?
What extra processing and/or tooling if any would need to be added to the API?
One thing I'm wary of is that we have some pretty heavy caching on common endpoints, so I'm concerned that we may not gain any efficiency from implementing this as a single user not using a webhook would have similar performance impact to everyone not using it.
I would like to contribute to the API by implementing a webhook system that can notify subscribed apps that an update to the database has happened, instead of requiring apps to make request after request to check if the API has been updated. Not all apps would benefit from this, but if there are any apps that only need data when an update has occurred, a webhook system is far more efficient.
Let me know if you would like my contribution on this
The text was updated successfully, but these errors were encountered: