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
Would it be possible to provide a sink that makes a request to a (local) HTTP server?
My use case is that I have a Node.js project that acts upon events on the Cardano blockchain. I'm currently using PostgreSQL notifications but would like to simplify the setup with Oura. HTTP would be a simple option, but if you can recommend other ways to receive Oura events in JS, I'm also interested.
I'm also specifically only interested in transactions (and their metadata and multi-asset info etc) to one specific Cardano address.
Thank you!
The text was updated successfully, but these errors were encountered:
@memewhale we have merged the code that introduces the new "webhook" sink. It will be shipped in the next release (later this week), but you can try it out if you build from source code.
You should be able to use it to call your Node.js service. We're still working on the documentation, but a minimal configuration of the sink would look like this:
[sink]
type = "Webhook"# url of your remote endpoint (needs to accept POST method)url = "http://localhost:5000/events"# value to add as the 'Authorization' http headerauthorization = "user:pass"# key-value map of extra headers to pass in each http call
[sink.headers]
extra_header_1 = "abc"extra_header_2 = "123"
Would it be possible to provide a sink that makes a request to a (local) HTTP server?
My use case is that I have a Node.js project that acts upon events on the Cardano blockchain. I'm currently using PostgreSQL notifications but would like to simplify the setup with Oura. HTTP would be a simple option, but if you can recommend other ways to receive Oura events in JS, I'm also interested.
I'm also specifically only interested in transactions (and their metadata and multi-asset info etc) to one specific Cardano address.
Thank you!
The text was updated successfully, but these errors were encountered: