ZeroTier configuration

Hi,
I’m about to build a integration where we are going to get data from a SQL server which is located in another network. At the location where the SQL server is they use ZeroTier. We want to use ZeroTier One and the api, I have created a account and I’am able to connect and join to a network and query the sql server in my test environment. My problem is that I am not able to get/set the information for an already authorized configuration. I have a local.conf file which I point to in the Node.InitFromStorage method.
Have browsed the C++ code and I cannot find where it reads from the configuration file. I see it points out the path to the file.

int zts_init_from_storage(const char* path)
{
ACQUIRE_SERVICE_OFFLINE();
zts_service->setHomePath(path);
return ZTS_ERR_OK;
}

Are we forced to have a ZeroTier client installed or is it possible to use the api standalone? More info, if I call the InitFromStorage method the code just stops waiting to get online.

Hi everyone, some friend and me was looking for some alternative that support LAN and zerotier was our salvation, we create a network and everything good but the latencys was really high (350-500ms Reply from 172.25.136.94: bytes=32 time=403ms TTL=64
Reply from 172.25.136.94: bytes=32 time=387ms TTL=64
Reply from 172.25.136.94: bytes=32 time=135ms TTL=64
Reply from 172.25.136.94: bytes=32 time=414ms TTL=64
Reply from 172.25.136.94: bytes=32 time=126ms TTL=64
Reply from 172.25.136.94: bytes=32 time=127ms TTL=64
Reply from 172.25.136.94: bytes=32 time=122ms TTL=64
Reply from 172.25.136.94: bytes=32 time=124ms TTL=64
Reply from 172.25.136.94: bytes=32 time=402ms TTL=64
Reply from 172.25.136.94: bytes=32 time=133ms TTL=64
Reply from 172.25.136.94: bytes=32 time=231ms TTL=64
Reply from 172.25.136.94: bytes=32 time=242ms TTL=64
Reply from 172.25.136.94: bytes=32 time=232ms TTL=64
Reply from 172.25.136.94: bytes=32 time=271ms TTL=64
Reply from 172.25.136.94: bytes=32 time=234ms TTL=64
Reply from 172.25.136.94: bytes=32 time=237ms TTL=64
Reply from 172.25.136.94: bytes=32 time=237ms TTL=64
Reply from 172.25.136.94: bytes=32 time=240ms TTL=64