Documentation for CODE@ExactTarget > Web Service Guide > API Release Changes > 143 Release API Changes

143 Release API Changes

    ExactTarget is excited to announce that we are enhancing the ExactTarget Web Service API as part of the 141 Release. Because these enhancements only add functionality - no functionality is being changed or removed - we do not expect this enhancement to affect your implementation as it currently exists. See a summary below of the use cases that will be supported by the enhancements.

    To provide more technical detail about the enhancements, ExactTarget maintains API documentation at http://docs.code.exacttarget.com/020_Web_Service_Guide. This online resource contains information and sample code regarding the applicable methods, objects, and properties, as well as technical articles and other support material. You can also join the ExactTarget 3sixty developer's community at https://3sixty.exacttarget.com to interact with other ExactTarget API developers and help each other build better code.

    Key Topics for the 143.5 Release

    This release offers enhanced performance and stability for tracking extracts.

    Key Topics for the 143.3 Release

    The 143.3 release provides improved system performance and bug fixes.

    Key Topics for the 143.2 Release

    The 143.2 release provides improved support for group retrieves and blackout attributes on triggered sends. The release also provides the ability to manage subscribers on a triggered send hidden list.

    Key Topics for the 143.1 Release

    The 143.1 release provides better messaging around using the correct endpoint to access the ExactTarget SOAP API WSDL.

    Key Topics for the 143 Release

    The 143 release enables new customers to use default names to identify sender profiles, delivery profiles, and send classifications in an email send definition:

    • New customer key for default sender profile = DEFAULT
    • New customer key for default delivery profile = DEFAULT
    • New customer key for default transactional send classification = Default Transactional
    • New customer key for default commercial send classification = Default Commercial

    Previously, the API required the numeric ID for these elements, and existing customers should continue to use these numbers in their API calls. This feature applies only to accounts created after October 7, 2011. This feature must be enabled for your account. Contact your ExactTarget representative for more information.

    The 143 release also adds improved permissions checking for creating and updating objects using the SOAP API.

     



    Was This Page Helpful?
    Suggestions or Comments:
    Name (optional):
    Email Address (optional):
    Enter 11280 backwards:
       
    Last Edit Date: 17:50, 2 Mar 2012
    Admin
    Powered by MindTouch