Hi @<1562973083189383168:profile|GrievingDuck15>
Thanks for noticing, yes the api is always versioned, we should make it clear in the docs. Also if you need the latest one use version 999 , it will default to the latest one it can support

So I tested using the version that I can see in the request going to the server, but the api returns "Requested version: 2.28, Used version 1.0" for some reason. I'm not sure if the message is wrong or it actually used 1.0.

Requested version: 2.28, Used version 1.0" for some reason

This is fine that means there is no change in that API

Weird . I recently implemented a function that talked to this exact endpoint and found it had to exclude the version and api paths . Is there some sort of redirect that happens?

Hi @<1593051292383580160:profile|SoreSparrow36> , it's not a redirect, it's simply the server using the latest version if you did not specify a version.

Regarding the original message, base_url refers to the API endpoint (in a self-served server, this would usually be with port 8008). The fact you had to use /api simply means you were using the WebApp endpoint which has its own apo reverse proxy, which should not really be used by external clients (it's possible, but there's no guarantee for backwards compatibility there as it's designed to be used by the WebApp and might change in the future)