Email Routing API commands always return 404

I have most of the API commands coded and working well on my system. I started to add the email routing options but it really does appear there is a bug in the API. These are new features, maybe no one noticed yet?

This command will always 404. I’ve tried with multiple domains and even multiple CF accounts.

Method: POST Enable Email Routing

curl -X POST

"" \
     -H "X-Auth-Email: [email protected]" \
     -H "X-Auth-Key: c2547eb745079dac9320b638f5e225cf483cc5cfdda41" \
     -H "Content-Type: application/json"

This is true with other email routing commands in the documentation. Always 404. I’ve checked my code backwards of forwards, and as I said it’s working on many other parts of the API system.

It works for me fine:

curl  --request POST '' \
--header 'X-Auth-Key: <Global API Key>' \
--header 'X-Auth-Email: <Admin Email>' \