The destinations service in Adobe Experience Platform uses configuration endpoints for several components that build up the destinations functionality. Combined, these components allow Experience Platform to connect to destination platforms, send custom messages, export custom files, and activate profile data across the digital ecosystem. The configurations used in Adobe Experience Platform Destination SDK are:
The pages below provide more detail about the functionality and configuration options available in Destination SDK, and the corresponding API operations that you can perform.
|Functionality description (streaming destinations)||Functionality description (batch destinations)||API reference|
|Destination configuration options||File-based destination configuration options||Destinations API endpoint operations|
|Server and template specs||Server and file configuration specs||Destination servers API endpoint operations|
|Authentication configuration||Same as for streaming destinations.||You can configure the authentication information for your destination via the
|Audience metadata management||Same as for streaming. See file-based example to understand how audience metadata can be used in a batch destination context.||Audience metadata endpoint API operations|
|OAuth 2 configuration||Same as for streaming destinations||Configure using the
|Testing tools for streaming destinations||Testing tools for file-based destinations||Destination testing API operations|
|Destination publishing||Same as for streaming destinations||Destination publishing API operations|
By reading this article, you now have a general overview of the functionality provided by Destination SDK and which pages to read for more information about specific configurations. Next, you can read the guides which include all the steps to configure a streaming or a file-based destination by using Destination SDK.