2017 --> This works!
cpapi2 --user=username Park park domain=example.com
On the
third post in the thread mentioned by sparek-3 in their third post. I noted that bmett was using cpapi2 and looked up the documentation:
cPanel API 2 Functions - Park::park - Software Development Kit - cPanel Documentation
Now there are a couple of very important things to note and cPanel associates should please take in to consideration for refining the documentation.
1.) I did not know that the subdomain parameter was
optional. The first parameter is mentioned as required. There should probably be a dedicated column to help visually differentiate this.
2.) The username likely will
not be root. In example a former host had my user name for cPanel as being
jabcre5. I was getting the
"
This feature is not enabled" error while trying to use the
root user.
3.) I always try to scale documentation and I have been a bit confused about how cPanel and WHM relate. I know that obviously if you're a reseller or higher you can have other people with access to their own "copy" of cPanel. This is more in regard to how to check if something is enabled and if an API is not enabled how to enable and even more important what level of permissions you need and how to check what level of permissions you're at. Let's say that there are five levels, 1~5, a feature requires level 3 access and you're level what...? Dead simple and if that information is there I simply do not see it.
4.) The general overview of the API documentation that lists like five or six versions of different things to do the same stuff (more or less) does not differentiate why one should use one thing over another or if one type of API is more appropriate for a context of a user. Shared, VPS and dedicated in example. It is exceptionally important to use standardized terminology to reduce confusion.
I will say I'm glad I need to do what I'm doing in 2017 and not ten years ago. There certainly has been a lot of hard work by the cPanel team on implementing support for various features. I think while there is a lot of documentation that the core issues I've mentioned really do the documentation a lot of injustice because once I get something working it works absolutely fantastic. I specialize in UX and human-PC interaction. I'm a power user and if something is prepared properly I can engage quickly and get stuff done. If the cPanel could make those changes to the documentation I think there would be a lot less confusion.
Thank you for the replies; I appreciate everyone's help and intentions.
