Forum

On Friday, 12 noon PST, we will be moving the API to a new server. This should improve the performance of both the API, and of our main site dynadot.com.

Please update your scripts as follows:

OLD API URL:

  https://www.dynadot.com/api.html

NEW API URL: (use this starting at Friday 12 noon PST)

  https://api.dynadot.com/api.html

There are no other changes to the API besides the page url.

PHP / CURL Is working fine for me. I can let it run for hours or days on end without much errors.

Occasionally I get the execution error, but it only appears a couple times before clearing up.

>Is it Friday 12 noon PST yet?

>No, it isn't.

The info about the new URL was posted on Thursday 22nd Jan so Friday 23rd Jan would have been when the new URL came into effect .. And, using the old URL prompts you to update to the new URL .. Thanks for the 'help' though.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

>Make sure you've entered the IP address into your Dynadot >API settings. If your IP isn't entered, the API server will >not respond to any of your requests.

IP is set to what it always was but still not getting a response from the API.

I'm still having problems with this.
Is cURL no longer able to be used with the API?

An example of the URL I'm using:
https://api.dynadot.com/api.html?version=1.0&key=KEY-GOES-HERE&command=search&domain0=dynadot.com&&domain1=dynadot.net


[This post has been edited by aiofe on Jan 30, 2009 12:36am.]

>The new URL (https://api.dynadot.com/api.html)isn't working for me at all ..
>are there problems with the API?

Is it Friday 12 noon PST yet?

No, it isn't.

-aiofe-

Make sure you've entered the IP address into your Dynadot API settings. If your IP isn't entered, the API server will not respond to any of your requests.

The new URL (https://api.dynadot.com/api.html)isn't working for me at all .. are there problems with the API?

Whatever it was (from what I've read it sounds like it could've been because of DDoS attacks on Network Solutions), it seems to be fixed now. The API is working just fine.

There seems to be something wrong with the API upgrade. Whenever I try to do lookups on .com and .net domains I get the error, "offline".

Here's an example result that I'm receiving back:

ok, domain0,blah.com,,offine, domain1,blah.net,,offine, domain2,blah.org,,no,

I figure it's more likely that this is a problem with the API upgrade, as opposed to the .com/.net registry actually being down (especially considering whois lookups on .com/.net are working fine everywhere else I've tried).

Thanks Dynadot!

Hope the speed increases with the new API server. It would be nice if the API went back to 1 second intervals between each server response.