Hi,

I've recently tried to employ the API toolkit provided by ResellerClub. The first problem that hit me was that they do not support php5 (which is the only activly maintained php version now!). Second thing was that the Perl API requires a version of SOAP::Lite not newer than 0.60. Even Debian ships with 0.69 by now. I've tried it with 0.69 and getting a java error message about an empty body.

Does anybody have an idea how I can get arround those problems or will I have to wait till directi hopefully releases the long overdue updates to those toolkits?

I am also waiting for DirectI to get their API kits to work with PHP5.

Every time I contact them they just say they are working on it.
They are very slow :disagree:

i was planning on use the api for a project and saw that 2 days ago, not supporting php5 has non sense, maybe i should send them a ticket asking, so this could put more pressure on them

Anyone else is going to send that ticket? ;-)

Why do you care what there toolkit supports and what not, that has nothing to do with the API. The API is as the name says an interface, you get the specifications and you can use any programming language you want.

Hey guys,

The PHP API does work on PHP5, some of the classes have been changed!!

We have it running aok on PHP5!

Regards,
Chris

@netearth: The documentation still states the pre-programmed examples and tool kits are PHP 4 only; though one can always write their own. That's not to say that they haven't actually updated them, just it doesn't show on their site.

@rony: Some people prefer to use an existing tool kit instead of writing their own classes to deal with API programming. Personally I'd rather know my system inside and out by writing my own code from scratch than use their existing code.

I'll take a look at the php5 support again, thanks for the hint.

Concerning Perl I've done a little testing with the propossed SOAP::Lite version in a testing debian sarge envoirment and here is what i got:

Using wrong credentials on debian sarge i get a correct error response when using the following piece of code:

#!/usr/bin/perl

use SOAP::Lite;

my $client = SOAP::Lite
-> service('file:/root/directi/lib/wsdl/DomOrder.wsdl'); # the wsdl file provided in the perl api kit

my $result = $client->getOrderIdByDomain("irecti-in\@domorder.com", "#########", "reseller", "en", 1, "t-azubi.net", "domcno");
#print $result;
my $som = $client->call();

if ($som->fault) {
print $som->faultcode, " !!!!!!! ", $som->faultstring, "\n";
}
else{
print $result;
}

It tells me:
soapenv:Server.userException !!!!!!! com.logicboxes.error.AuthenticationException#~#com.logicboxes.foundation.sfnb.Authentication#~#Invalid Password/Username, or your User account maybe Inactive or Suspended#~#warn#~#

On the other hand, when I run the exactly same code on Debian Etch (my prefered platform) I allways get the following message:

soapenv:Server.userException java.lang.Exception: Body not found.

When I use correct credentials on etch and query for result, than I get the expected result, but the $fault boolean is allways TRUE, so I can't decide if there was an error or not. Has anybody an idea what to do about it?

For some time now, we've been in the process of gradually phasing out the SOAP API and have now introduced an HTTP API.

You can use the existing HTTP libraries available in almost all programming languages and try out or test the API using any browser.

For more information on the HTTP API, please visit http://manage.resellerclub.com/kb/answer/744

For some time now, we've been in the process of gradually phasing out the SOAP API and have now introduced an HTTP API.

You can use the existing HTTP libraries available in almost all programming languages and try out or test the API using any browser.

For more information on the HTTP API, please visit http://manage.resellerclub.com/kb/answer/744

wow, nothing like digging up a thread that is over 2 years old... Once you have made the http api, as good or better than the soap api, I would start singing about it... Last time I checked it is missing quite a few calls, and last I played some of the existing ones do not even work properly (you have been notifed of these and did fix them).

I understand that from a seo perspective this thread maybe against their concept and perhaps even harmfull. sorry for the perhaps a bit dramatic title.

about the LogicBoxes API today: "We will be deprecating the SOAP API in a few months. If you are planning to use the SOAP API or are already using it, we recommend that you use our flexible, powerful and simple HTTP API." on the other hand we have the HTTP API which according to your documentation is still beta.... great.

I also miss some function in the http api which I did notify your support about a long time ago: checking transferability of a domain (older than 60 days, still locked?) and the modify company command for .eu domains to name just a few.

Also the documentation of the response values is very poor... as a developer you basically have to test each and every call in order to evaluate the possible JSON output.

I understand that from a seo perspective this thread maybe against their concept and perhaps even harmfull. sorry for the perhaps a bit dramatic title.

about the LogicBoxes API today: "We will be deprecating the SOAP API in a few months. If you are planning to use the SOAP API or are already using it, we recommend that you use our flexible, powerful and simple HTTP API." on the other hand we have the HTTP API which according to your documentation is still beta.... great.

I also miss some function in the http api which I did notify your support about a long time ago: checking transferability of a domain (older than 60 days, still locked?) and the modify company command for .eu domains to name just a few.

Also the documentation of the response values is very poor... as a developer you basically have to test each and every call in order to evaluate the possible JSON output.

@petzsch: the HTTP API while already being used by many partners on the platform, is still work-in-progress in terms of tweaks that we do plan on making for responses etc. We have sent you a PM with responses to the specific questions you have put forward.

wow, nothing like digging up a thread that is over 2 years old... Once you have made the http api, as good or better than the soap api, I would start singing about it... Last time I checked it is missing quite a few calls, and last I played some of the existing ones do not even work properly (you have been notifed of these and did fix them).

@netearth: we are not looking to discontinue the SOAP API until all calls are exposed in the HTTP version. While the customer and domain specific API calls have already been exposed in the HTTP API, the Reseller specific API calls are work under progress and will be made available eventually.

By digging up a 2 year old thread I think it speaks in volume that RC is 2 years behind.

They aren't the only ones however.

Our thoughts and prayers go out to the hostgator customers that are going to see how RC/LB works, or doesn't...............

Please correct me if they are in fact separate entity's, im under the assumption they are not.