When you say you are trying to get to the 3CX API, and at the same time you are tinkering with the 3CX ini file, I'm wondering what API you are trying to access. Perhaps an explanation of what you are trying to achieve would help us provide appropriate guidance.
Having said that, tinkering with the 3CX ini file is NOT supported. As a 3rd-party developer, we asked whether we could make a 1 character change to the in, and 3CX offered a very STRONG NO! My advice is that you revert all your changes and go in a different direction.
The only 3CX API available at this time is the 3CX Call Control API and tinkering with the ini is not going to enable you to access the API. The API only responds to requests from Localhost, and that cannot be changed. Further, as you have probably already discovered, 3CX has withdrawn the documentation for the Call Control API presumably in preparation for the newly announced REST API and Gateway service scheduled for release shortly after the initial release of 3CX V18. This will be the supported approach to integrating with 3CX going forward.
OK, so tells us what you are trying to accomplish -- then we can offer some guidance.
