I hope this is the correct spot and that I am not missing something, that would be embarrassing Also tried to search for that issue, but I could not find something so far (https://tickets.metabrainz.org/browse/MBS-3815?filter=-4&jql=text+%7E+%22playing-now+recording_mbid%22+order+by+created+DESC)

I am currently trying to make a bot that lets people easily share what song they are currently listening to and what past songs they listened to. While implementing that I realised that /1/user/(user_name)/playing-now API (https://listenbrainz.readthedocs.io/en/latest/users/api/core.html?highlight=playing#get--1-user-(user_name)-playing-now) is not including a recording_mbid in the response. Meanwhile you have that property in the payload that you get as a response from /1/user/(user_name)/listens (https://listenbrainz.readthedocs.io/en/latest/users/api/core.html?highlight=playing#get--1-user-(user_name)-listens)

The documentation for playing-now does mention, that the result should be equal to the listens-api ("This endpoint returns a JSON document with a single listen in the same format as the /user/<user_name>/listens endpoint, with one key difference, there will only be one listen returned at maximum and the listen will not contain a listened_at element."). So I guess that it is not intended that this property is missing?