Dynadot API – More Spending Means More Registry Connections


Dynadot LLC

Dynadot API Connections

Dynadot is one of the more popular registrars that offers an API for registering domain names. Domainers have been using Dynadot as their preferred registrar while drop catching expired domains via the API. Beginning this year in January 2012, Dynadot decided to open up it’s API to all users.  Before 2012, users were required to spend $500 USD yearly to qualify for a bulk account that allowed API access. As of January, all users received access to using the API & the $500 yearly still qualified your account as bulk – but only offers bulk pricing on each domain registration’s price.

Since the API has been opened up to all users, Dynadot has implemented API connection restrictions based on each member’s spending. This means that users who spend more, receive more live connections to the central registry (Verisign) which secures more connections for drop catching expired domain names.

The general feedback from domainers is that Dynadot no longer offers a suitable API for their drop catching needs. I often get emails about the Dynadot dropking.com software that users often see the API return a: “System_Busy” error. Sometimes this is all they see in the drop catching activity log. Some people have given up on the API completely and moved on to drop catch names at Moniker or other registrars offering an API.

While Dynadot’s API is currently over subscribed, they are working on obtaining more registry connections for drop catching expired domains. According to Dynadot’s president: Todd Hann, additional registrar connections are on the way soon. So don’t lose hope on using this API for your drop catching needs. As soon as more connections are made available, drop catching should pick up for domainers who utilize this API.

So what happens now for users who have pre-funded their Dynadot accounts & still want to catch expired domains? After some digging around, I found this information from Dynadot’s support team. This basically covers how Dynadot’s API works & what you can expect from your spending and what to expect to catch using their API.

This table describes an example if six customers were accessing Dynadot’s API at the same time – based on their yearly spending habits. Notice that the live registry / API connections Dynadot is allowed are linear with each member’s yearly spending:

Dynadot.com’s Spending API Access Scale
Your Account Spending Per Year Allocated API Connections
$5,000 5,000
$2,000 2,000
$1,000 1,000
$500 500
$100 100
$1 1
$0 0

I do get good emails from users who are sucessfully catching domains with Dynadot & their secret is to keep adding funds to their accounts on a daily basis. These drop catchers are throwing in $20-$40 daily & successfully catching approx 2-4 domains a day. Therefore securing more connections to the central registry for drop catching domains they desire. This in fact keeps adding connections to the user’s account from the pool.

I feel a lot of domainers have lost hope in Dynadot’s API, but you shouldn’t. If you look at the whole picture and invest on a daily basis, you will find that the Dynadot API can be a useful tool you can depend on for your daily drop catching activity.

If you have any questions or want to get involved in catching expired domains with Dynadot’s API, you can contact me at any time or checkout the tools for sale at DropKing. I’m more than happy to help with anything I can to make your drop catching experience successful.

Happy Domaining!!

You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.


  • Zap says:

    I don’t get it. What does “Allocated API Connections” means?

    The number of simultaneous connections? of course not.
    The number of successful hits Per hour? Per day?

  • admin says:

    Hi Zap, Allocated API Connections means the total connections in X amount of time. In this example – in however long of time 8,601 connections are allocated – the connections would be split up across these users. So across this example at 4 registry connections per second, Across 35 minutes, these connections would be dispersed per member as the chart shows. Hope that makes sense, let me know if it doesn’t & I will try to explain better.

  • Zap says:

    I am sorry, but this is not easy to understand.

    Let’s say I hit the Dynadot API with 1,000 hits in one hour.

    You’re saying the $1000 user get’s no System_Busy error, and the $100 user get’s 1 out of 10 no System_Busy errors?

    How about the next hour? Will the $1000 user get ALL System_Busy errors? (since his quota is over?!)

  • admin says:

    I am not 100% sure, but I believe Dynadot would rotate the system_busy errors across all accounts. So the $1,000 user would get a system_busy error across the other user’s tries which would be 5 system_busy errors if i’m not mistaken. The $100 user would get 905 system_busy errors in the same cycle. The system cycles so the next hour wouldn’t matter & the cycle would continue – depending on how many people are hitting the API.

    I am not all that sure about the above. It would be nice if Dynadot can chime in on their system & how it works. Although the above makes sense to me systematically, it may be that Dynadot implements a whole different math cycle to disperse the registry connections.

  • missdot says:

    Hi there,

    The priority queue is how we implement the connection allocation. The API requests are given a priority score. This score is the total spending divided by the connections received by the account in the last 24 hours. An account with high spending that gets a lot of connections will get a lower priority score over time to allow lower spending accounts to get access to connections as well.

    All API requests are put into a queue and are sorted by their priority score. Once a connection becomes available, the user with the highest priority score is removed from the queue and given the connection. If a request is not given a connection after 10 seconds, a “system_busy” response is returned.

    Dynadot Team

  • admin says:

    Dynadot, thank you for the connections explanation. I hope it helps users in understanding your API better & how it works.



Leave a Reply

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>