Delivery API overview

Last update: July 17, 2023

CREATED FOR:

  • Developer

The Adobe Target Delivery API is based on REST. This documentation describes the resources that make up the Adobe Target Delivery API. HTTP methods are utilized to execute operations on those resources.

Using Adobe Target’s Delivery API, you can:

  • Deliver experiences across web, including SPAs, and mobile channels as well as non-browser based IoT devices such as a connected TV, kiosk, or in-store digital screen.
  • Deliver experiences from any server side platform or application that can make HTTP/s calls.
  • Deliver consistent and personalized experiences to a user no matter which channel or devices the user has engaged with your business.
  • Cache experiences for a user within a session in your server so that multiple API calls can be avoided and as a result achieve better performance.
  • Seamlessly integrate with Adobe Experience Cloud products such as Adobe Analytics, Adobe Audience Manager, and the Experience Cloud ID Service from the server side.

For more information, see the Adobe Target Delivery API documentation.

NOTE
You can still access the legacy /v1/mbox and /v2/batchmbox API documentation. However, features will be developed in the Delivery API (as documented here) that will not be backported to the legacy APIs.
Previous pageConfigure authentication for Target APIs
Next pageSDKs to interact with the Delivery API

Target