SOLVED DomainInfo stopped working

[jimlongo]

I've been running into some problems since a recent update to WHM. On today's agenda is a call i've been making for years from WHMCS using a curl call to WHM UAPI.

GET to

https://myserver.com:2087/json-api/cpanel?cpanel_jsonapi_user=someuser&cpanel_jsonapi_module=DomainInfo&cpanel_jsonapi_func=list_domains&cpanel_jsonapi_apiversion=3

Authentication is in the header with an access token.

Now I'm getting a 301 response in WHMCS.

When I test the call in Postman I get a 200 with the following error

{"cpanelresult":{"module":"DomainInfo","error":"Could not find function 'list_domains' in module 'DomainInfo'","apiversion":2,"data":{"result":0,"reason":"Could not find function 'list_domains' in module 'DomainInfo'"},"func":"list_domains"}}

 

[cPRex]

Hey there! I'm not aware of anything that has changed recently on the cPanel side related to this call. I do see you are using port 2087 instead of port 2083, so you may want to consider adjusting that.

We have an example of a Curl request with a token that was provided by one of our developers here:

WHM API 1 - Basic Test failing 403

Hello, I am doing a basic call to whm api 1 by following documentation https://documentation.cpanel.net/display/DD/Guide+to+WHM+API+1 I have created the api token from whm panel. And trying to do a get request via Postman to get an user account statistics. GET...

forums.cpanel.net

so it might be worth comparing that to how your curl command is configured to see if that matches.

 

[jimlongo]

Thanks for the reply, that did end up helping by giving me some things to look at.

The port I have is correct, it needs to be 2087 for this type of call.

My problem (just in case it helps someone else) is in WHMCS I was getting the information to make the call ($protocol, $hostname,$username,$secure) from the table `tblservers` which is the list of connected provisioning servers.

I was using the $secure variable to decide whether to use the http or https protocol in the url I'm calling.

It looks like this setting in the db should have the values of "on" or "off", but somehow in my DB had changed to a value of 1.
So my call was using http . . .

 

[cPRex]

Well that's definitely odd, but glad you were able to track it down!