Transition from Target Classic APIs to Target APIs on the Adobe Developer Console
Information to help you transition from the Target Classic APIs to the Target APIs on the Adobe Developer Console.
With the decommissioning of Adobe Target Classic, the APIs connected to your Target Classic account have also been made unavailable. This article will help you transition your Target Classic API-based integrations to the Target APIs powered by the Adobe Developer Console.
For more information about Target APIs, see Target APIs. For more information about Target SDKs, see Target Server-side Implementation
Terminology
testandtarget.omniture.com
. If your API calls contain a user name and password in the request URL, you must transition to the Adobe Developer Console APIs.Timeline
The following APIs were decommissioned when Target Classic was decommissioned:
All API methods that perform a write operation (saveCampaign
, copyCampaign
, saveHTMLOfferContent
, and setCampaignState
) were decommissioned.
This is the same date when all Target Classic user accounts were set to read-only status.
Recommendations Classic APIs were not impacted by this timeline.
Equivalent Methods
The following table lists the equivalent Adobe Developer Console API methods for the Classic API methods. The Adobe Developer Console APIs return JSON, whereas the Classic APIs return XML.
The Adobe Developer Console API methods are linked to the corresponding section in the API documentation site. An example is provided for each API method. You can also use the Target Admin API Postman Collection that contains sample API calls for all the Adobe API methods on the Adobe Developer Console.
Exceptions
If you require an exception, please contact your Customer Success Manager.
Help
Please contact Adobe Target Client Care (tt-support@adobe.com) if you have any questions or need help transitioning from the Classic APIs to the Target APIs on the Adobe Developer Console.