Hey, that data is missing because it was not present in beatmap at the time of parsing. It will show up when will become available. Also multiple requests is not a problem.Woddles wrote:
Hey, first of all I just wanted to say great job on the API. It's extremely helpful for me, having data request via MD5 hash.
One problem I ran into though, is when using the metadata request (Example: http://api.osu.miz.hexide.com/metadata/9e63d9a0b139c5953101e5eaf77af809), 'm_beatmap' and 'm_beatmapset' don't seem to be displaying (Image example).
Any chances this could be fixed? Would be extremely helpful so I only have to make a single request rather than multiple per map.
Thanks!