Content Language preferences seems to work 99% on desktop, but doesn't make it through to browsing via Voyager. The Voyager Dev asks if the issue may be that Content Language preferences aren't being passed to the API yet.

Can someone provide information if this is the case or not? If not, can you provide thoughts on what the issue may be?