All affected endpoints have been restored to their correct configuration and the API is fully operational again.

API endpoints were accidently mapped incorrectly, causing unexpected behavior. Our team is actively investigating the issue and working on a fix.