Edit in GitHubLog an issue

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 document 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


Classic APIAPIs that are linked to your Target Classic account. These API calls are based on a username and password-based authentication and use the hostname 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.
Adobe Developer ConsoleThe Adobe Developer Console is the gateway for Target APIs. These APIs are connected to your Target Standard/Premium account. The Target APIs on the Adobe Developer Console use a JWT-based authentication, which is the industry standard for secure enterprise APIs.


The following APIs were decommissioned when Target Classic was decommissioned:

October 17, 2017All 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.
November 14, 2017The remaining APIs were decommissioned. This is the date when the Target Classic user interface was decommissioned

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.

GroupingClassic API MethodAdobe Developer Console API MethodNotes
Campaign/ActivityCampaign CreateCreate AB Activity
Create XT Activity
The new APIs provide separate create methods for AB and XT
Campaign UpdateUpdate AB Activity
Update XT Activity
Copy CampaignN/AUse the Activity Create APIs
Campaign ListList Activities
Campaign StateUpdate Activity State
Campaign ViewGet AB Activity by ID
Get XT Activity by ID
Third-Party Campaign IDN/AIf you are using a thirdpartyID, the relevant Activity methods can be used
OffersOffer CreateCreate Offer
Offer GetGet Offer by ID
Offer ListList Offers
Folder ListN/AFolders aren’t supported in Target Standard/Premium
ReportingCampaign Performance ReportGet AB Performance Report
Get XT Performance Report
Audit ReportGet Audit Report
1-1 Content ReportGet AP Performance Report
Account SettingsGet Host GroupsList Environments


If you require an exception, please contact your Customer Success Manager.


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.

Was this helpful?
  • Privacy
  • Terms of Use
  • Do not sell my personal information
  • AdChoices
Copyright © 2022 Adobe. All rights reserved.