It is quite annoying that there’s no universal consistency when it comes to the order of coordinates. It seems like the standard for GeoJSON is indeed [Longitude, Latitude] ( RFC 7946 - The GeoJSON Format (ietf.org)), but I’m guessing the API might not use this order because the majority of map software (e.g. Leaflet, Google Maps API, Google Maps SDKs, Apple MapKit, etc) all use [Latitude, Longitude] ( lon lat lon lat lon - macwright.com), so it’s easier to integrate the API into third party maps.
There isn’t really a consistency on which is “correct”, but I guess since the API uses the GeoJSON format it should conform to its [lon, lat] format. Though changing this now is likely to break a lot of existing software.