You guys have an interesting project with a great looking presentation. Since we’re built with the same technologies (.NET, windows/linux/osx via Mono), I thought I’d stop in and say hello.
It was brought to my attention that you have an item on your trello board relating to talking to us after successful downloads. If I can be of any assistance, please let me know. Thanks.
Luke
It’s good to see these 2 great applications talking to one another.
Hey @luke thanks for stopping by!
I took a quick look at the API docs on the wiki but didn’t immediately see a section on updating the library, could you point me at that? And is there a UI notification system in MB, where a text notification can be displayed (like a toast popup when someone messages you in an IM client).
Yea, we have that. The following api was designed for Sickbeard based on what they asked for, but it should cover your needs too:
Notify MBS that a new series was added
POST
/mediabrowser/Library/Series/Added?tvdbid=xxx
Notify MBS that an existing series was updated (e.g. metadata update or new content added):
POST
/mediabrowser/Library/Series/Updated?tvdbid=xxx
Generic notification to administrative users:
POST
/mediabrowser/Notifications/Admin?Name=Name&Description=Description&ImageUrl=xxx
Alternatively you can also post this using a request body of contentType application/json, which will probably be preferred given if using description param. For example:
POST
/mediabrowser/Notifications/Admin
Body:
{
Name: “xxx”,
Description:“xxx”,
ImageUrl: “xxx”
}
The notifications will be handled by the server’s notification system, and will be send to the various notification services that the user has configured.
Any progress please?
Progress is tracked on Trello.
No updates on there.
Never mind.
Thanks.
Nice to see MB making a appearance in Drone and hope to see collaboration in between both products to make the media center management experience even more complete 
Hey guys, we are tightening up our api security, so this is likely going to require the user to configure with either credentials or an api key. I will update once finalized.
Fyi guys, the security improvements are done.
All of the above information still applies, except you’ll need to add a user-configured api key to every request.
api_key = xxx
@luke I’m able to send notifications by POSTing the JSON body as you described, but I get a 404 for the Library update call, I’m using the latest stable release (3.0.5326.13255). I tried with RestSharp (in code) and Postman (Chrome plugin), you can see the code here: https://github.com/NzbDrone/NzbDrone/blob/mediabrowser/src/NzbDrone.Core/Notifications/MediaBrowser/MediaBrowserProxy.cs
I took a look at the code and I was able to do a GET call to /Library/MediaFolders and received a valid response (wanted to test that other Library endpoints were working correctly).
Ah - apologies. Your code is fine. There is no handler receiving that endpoint. It will be resolved for the next server release. (And next dev build coming in the next day or two if you want to test).
Our next release will be soon so it won’t be much of a wait until the fix is public. Thanks.
Thanks @luke - I’ll try the beta release in the next few days and confirm its working (I assume thats the dev version).
Hi Markus.
Did you have time to test?
Just asking, as the series.xml file now being created by NzbDrone for MediaBrowser3, is not being recognised by the server.
@Luke should be able give more detailed reasons why.
Thanks.
No, I haven’t tried again, but we haven’t changed anything about series.xml for MB3 since it was added.
I believe that something has changed in Mediabrowser, so it now needs a Season folder instead of a series.xml file.
The MediaBrowser Server will then get metadata etc and create the xml file.
If this thread is about notifying MBS of a new series, then I presume the season folder won’t be needed either.
Does XBMC metadata work? Looks like support for it was added in the latest MB3 release.
Drone doesn’t notify on add, just when files are updated, the series will already need to exist in MB3 for that that to work I imagine (based on how their endpoint looks), even their add endpoint only takes in a TVDB ID, so presumably it needs something there to know when folder is the one for that TVDB ID.
The presence of a season folder instead of a metadata file to add the series to MB3 is a downgrade, the fact that either must exist for the series to be scanned in is awkward at best, so I hope thats not the case.
Regardless, we have no plans to create an empty season folder when adding a series.
Looks like the methodology for identifying a TV show is now via a Season folder - the series.xml file is no longer used to recognise a TV show.
I’ve tried this with both NzbDrone and SickBeard and it’s only when there is a season folder will MediaBrowser fetch metadata.
Hi guys,
Just letting you know the new release is up so you the api endpoints will now be available. Thanks.
@luke that’s the beta release? I was just testing it out, it no longer errors, but media browser doesn’t seem to rescan the series on dusj and update it.