API v0 end of life and API v1 2FA timelines
- API v0 will be shut down on October 31st, 2014. After that date you will not be able to send API requests to
dnsimple.comhostname, you will need to use our API hostnames as explained here.
- API v1 will no longer accept HTTP basic auth requests for accounts with 2FA enabled, unless you properly use the exchange token for authentication as described in our documentation.
Any customers who have performed an API call in the last two months will be sent a final notification email of the shutdown. You will be encouraged to upgrade to the newer v1 API and will need to support 2FA for clients that have it enabled. Just to be clear; at the end of October, any integrations using the older v0 API will no longer work.
Official DNSimple products and clients have been upgraded to support these changes. Here's the minimum required versions:
- DNSimple Ruby Client - Upgrade to 1.6 or greather for full support to v1 and 2FA
- DNSimple iOS Application Upgrade to 3.1 or greater for 2FA support
If you have any questions about this change, please email firstname.lastname@example.org.
Italian software developer, a PADI scuba instructor and a former professional sommelier. I make awesome code and troll Anthony for fun and profit.
We think domain management should be easy.
That's why we continue building DNSimple.
What's in a DNS response?
DNS queries and responses fly across the internet all day, but we don't often take a look at what's inside of them. Today we do.
Get Stronger Account Protection with Web Authentication (WebAuthn) Support
Protect your DNS assets and get stronger MFA with DNSimple's support for the Web Authentication API.