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
Send the events with json data to a given url. This will reduce the custom API implementations like gpodder and make it more generic. Anyone can implement the server part.
Example: played event
{
"specversion" : "1.0",
"type" : "played",
"source" : "antennapod",
"id" : "A234-1234-1234",
"time" : "2018-04-05T17:31:00Z",
"datacontenttype" : "application/json",
"data" : {
"episode":{
"title":"Title of podcast episode",
"url":"url of the episode",
"media":"url of the media",
},
"podcast":{
"title":"podcast title",
"feed":"feed url"
}
}
}
The text was updated successfully, but these errors were encountered:
This is a very technical feature that most users do not understand. It is really time-consuming to implement because we would need to handle network loss and failed hooks. You can already change the URL of the gpodder instance and their API is documented. You can build a server with the same API that just uses the played event or host gpodder yourself.
Send the events with json data to a given url. This will reduce the custom API implementations like gpodder and make it more generic. Anyone can implement the server part.
Example: played event
The text was updated successfully, but these errors were encountered: