Is this a new thing or has this always been the case?

Looks like the API resolves the ID fine manually (where I've seen it resolve incorrect IDs before):...