Hello!
Thanks for your answer. I understand it may be difficult to match partial information like a track name with a recording MBID. That’s why MBIDs are for, after all!
But my point is more when the client already knows the track MBID. Today, it has to send a recording MBID and unfortunately it is less precise, and more difficult to match when synchronizing listens, as I said in the first post.
So, would it be possible to identify a listen using a track MBID, and get it back when getting the listens?
Ah! Looking for JSON Documentation — ListenBrainz 0.1.0 documentation just makes me realize this is already handled using the track_mbid field in additional_info so everything is fine 