Deprecation of Legacy Internal APIs

Version 1

    What we are announcing


    Effective immediately, we will be deprecating several internal-only, unsupported APIs.  While we've never publicly released or supported these APIs, we recognize developers may have discovered and built integrations and applications on top of them, and so we are providing advanced notice of their shutdown.


    APIs that are a part of this announcement include the following:

    • REST 0.9
    • REST 1.1
    • Data 1.0
    • Scoring 1.0

      

    These APIs will remain available for the next 6 months, with basic availability and security fixes only.

     

    These APIs will be deleted on January 1, 2016.

     

    Next steps for Developers


    Any developer consuming these APIs should switch to another RESTful API immediately.

     

    API-specific information:


    REST 0.9

    The entire API will be decommissioned.

    Requests to /API/REST/0.9/* will return 404.

    Most functionality in REST 0.9 is available in REST 2.0 at the same endpoints.  Most consumers should be able to simply replace "/API/REST/0.9" with "/API/REST/2.0" without additional changes.  Be aware that REST 2.0 is currently unsupported, and may change in future releases.    


    REST 1.1

    The entire API will be decommissioned.

    Requests to /API/REST/1.1/* will return 404.

    All functionality in REST 1.1 is available in REST 2.0 at the same endpoints.  Most consumers should be able to simply replace "/API/REST/1.1" with "/API/REST/2.0" without additional changes.  Be aware that REST 2.0 is currently unsupported, and may change in future releases.


    Data 1.0

    The entire API will be decommissioned.

    Requests to /API/Data/1.0/* will return 404.

    Contact management functionality is available in both REST 1.0 and REST 2.0.  Be aware that REST 2.0 is currently unsupported, and may change in future releases.


    Scoring 1.0

    The entire API will be decommissioned.

    Requests to /API/Scoring/1.0/* will return 404.

    All functionality in Scoring 1.0 will be merged into REST 2.0 in our 473 release and will be available at the same endpoints.  (/API/Scoring/1.0 will be an alias for /API/REST/2.0 during the deprecation period.)  Consumers should be able to simply replace "/API/Scoring/1.0" with "/API/REST/2.0” without additional changes.  Be aware that REST 2.0 is currently unsupported, and may change in future releases.

     

    If you have questions, post a discussion to Code It!