API v1 Blackout Dates and EOL January 6, 2014

As you may know, we are retiring use of our v1 API (we released v2 of the API in February 2012 and and have been working to close any parity issues in advance of its official end of life on January 6, 2014).

As part of this process, we’re starting an ongoing cadence of mini-blackouts for v1 API. This means that on the following dates, requests on v1 containing basic auth headers will be rejected:

December 10, 2013 9-11AM PST

December 12, 2013 1-3PM PST

December 17, 2013 9-11AM PST

For customers still using v1 API:

Please look for a proactive ticket from Zendesk Support Wednesday, November 27, 2013, which will let you know that your service may be interrupted. If you still need more time to migrate, please respond to that ticket so we can help you switch over to the v2 API.  There are known applications such as JIRA, Salesforce, and our mobile applications that still make use of API v1. Traffic originating from those sources will be unaffected. Otherwise, all other basic authenticated calls to v1 will fail during the blackout periods, returning a response code “HTTP 400 API v1 is disabled” .

As always, we’re here to help! Please reach out to api@support.zendesk.com with any questions or concerns.

-DeVaris

Have more questions? Submit a request

Comments

  • Avatar
    Travis Swientek

    What about an endpoint like "https://domain.zendesk.com/reports/22041026.json"? I was looking through the developer docs and couldn't find a similar endpoint. Is this even an API endpoint? 

  • Avatar
    David Blondeau

    I am an administrator on our account but did not get a proactive ticket from Zendesk so we got hit by this "mini-blackout". I get the fancy marketing newsletter but not the important stuff like this! And it feeks it is not the first time it happens. Why? Is there some setting I need to change to get those notifications?

    Thanks,

    David

  • Avatar
    DeVaris Brown

    Hi David,

    If you subscribe to this forum, you'll get all the notifications about everything dealing with the API. 

  • Avatar
    Joanna Bellis

    We are hugely annoyed and disappointed that we didn't receive a proactive ticket from Zendesk and only found out about this due to a number of errors in ticket creation, and having to search for answers in your blog.  

    I and others in my team have logged 3 tickets of high or urgent priority over the past 8 days with no response to two tickets (the one response we did receive said that our issues was more complicated and had escalated to someone else for assistance, who came back saying we had made a change to the API which has caused it not to work.  Nothing further to our response to that).  

     

    I would REALLY appreciate someone responding to us as soon as possible please.  At present we are looking at other alternatives to manage our support.  Thanks

  • Avatar
    DeVaris Brown

    Hi Joanna,

    I'm sorry for the inconvenience this has caused you. We've temporarily resolved this issue for you in the tickets you submitted. Going forward can you make sure that the technical/development contact for your organization is subscribed to the API Update forum?

    https://support.zendesk.com/forums/20635666-api-updates

    And our developer newsletter? 

    http://developer.zendesk.com/newsletter/signup.html

    That way any communication we have around our API will not be missed.

  • Avatar
    Joseph London

    Hello, 

    Has this off as anticipated?

Please sign in to leave a comment.