Create a destination server configuration
Creating a destination server is the first step in creating your own destination with Destination SDK. The destination server includes configuration options for the server and templating specs, the message format, and the file formatting options (for file-based destinations).
This page exemplifies the API request and payload that you can use to create your own destination server using the /authoring/destination-servers
API endpoint.
For a detailed description of the capabilities that you can configure through this endpoint, read the following articles:
Getting started with destination server API operations get-started
Before continuing, please review the getting started guide for important information that you need to know in order to successfully make calls to the API, including how to obtain the required destination authoring permission and required headers.
Create a destination server configuration create
You can create a new destination server configuration by making a POST
request to the /authoring/destination-servers
endpoint.
platform.adobe.io/data/core/activation/authoring/destination-servers
API format
POST /authoring/destination-servers
Depending on the destination type that you create, you need to configure a slightly different type of destination server.
Create static schema destination servers static-destination-servers
See in the tabs below examples of destination servers for destinations which use static schemas.
The sample payloads below include all parameters supported by each destination server type. You do not need to include all the parameters in your request. The payload is customizable based on your needs.
Select each tab below to view the corresponding API requests.
Create a real-time (streaming) destination server
You need to create a real-time (streaming) destination server similar to the one shown below when you configure a real-time (streaming) API-based integration.
accordion | ||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Request | ||||||||||||||||||||||||||||||||
|
accordion |
---|
Response |
A successful response returns HTTP status 200 with details of your newly created destination server configuration. |
Create an Amazon S3 destination server
You need to create an Amazon S3 destination server similar to the one shown below when you configure a file-based Amazon S3 destination.
accordion | |||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Request | |||||||||||||||||||||||||||||
|
accordion |
---|
Response |
A successful response returns HTTP status 200 with details of your newly created destination server configuration. |
Create an SFTP destination server
You need to create an SFTP destination server similar to the one shown below when you configure a file-based SFTP destination.
accordion | |||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Request | |||||||||||||||||||||||||||||||||||
|
accordion |
---|
Response |
A successful response returns HTTP status 200 with details of your newly created destination server configuration. |
Create an Azure Data Lake Storage destination server
You need to create an Azure Data Lake Storage destination server similar to the one shown below when you configure a file-based Azure Data Lake Storage destination.
accordion | |||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Request | |||||||||||||||||||||||
|
accordion |
---|
Response |
A successful response returns HTTP status 200 with details of your newly created destination server configuration. |
Create an Azure Blob Storage destination server
You need to create an Azure Blob Storage destination server similar to the one shown below when you configure a file-based Azure Blob Storage destination.
accordion | |||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Request | |||||||||||||||||||||||||||||
|
accordion |
---|
Response |
A successful response returns HTTP status 200 with details of your newly created destination server configuration. |
Create a Data Landing Zone (DLZ) destination server
You need to create a Data Landing Zone (DLZ) destination server similar to the one shown below when you configure a file-based Data Landing Zone (DLZ) destination.
accordion | |||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Request | |||||||||||||||||||||||
|
accordion |
---|
Response |
A successful response returns HTTP status 200 with details of your newly created destination server configuration. |
Create a Google Cloud Storage destination server
You need to create a Google Cloud Storage destination server similar to the one shown below when you configure a file-based Google Cloud Storage destination.
accordion | |||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Request | |||||||||||||||||||||||||||||
|
accordion |
---|
Response |
A successful response returns HTTP status 200 with details of your newly created destination server configuration. |
Create dynamic schema destination servers dynamic-schema-servers
Dynamic schemas allow you to dynamically retrieve the supported target attributes and generate schemas based on your own API. You need to configure a destination server for dynamic schemas before you can configure the schema.
See in the tab below an example of a destination server for destinations which use dynamic schemas.
The sample payload below includes all parameters required for a dynamic schema server.
Create a dynamic schema server
You need to create a dynamic schema server similar to the one shown below when you configure a destination that retrieves its profile schema from your own API endpoint. As opposed to a static schema, a dynamic schema does not use a profileFields
array. Instead, dynamic schemas use a dynamic schema server which connects to your own API from where it retrieves the schema configuration.
accordion | |||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Request | |||||||||||||||||||||||||||||
|
accordion |
---|
Response |
A successful response returns HTTP status 200 with details of your newly created destination server configuration. |
Create dynamic dropdown destination servers dynamic-dropdown-servers
Use dynamic dropdowns to dynamically retrieve and populate dropdown customer data fields, based on your own API. For example, you could retrieve a list of existing user accounts which you want to use for a destination connection.
You need to configure a destination server for dynamic dropdowns before you can configure the dyamic dropwdown customer data field.
See in the tab below an example of a destination server used to dynamically retrieve the values to be displayed in a dropdown selector, from an API.
The sample payload below includes all parameters required for a dynamic schema server.
Create a dynamic dropdown server
You need to create a dynamic dropdown server similar to the one shown below when you configure a destination that retrieves the values for a dropdown customer data field from your own API endpoint.
accordion | ||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Request | ||||||||||||||||||||||||||||||||
|
accordion |
---|
Response |
A successful response returns HTTP status 200 with details of your newly created destination server configuration. |
API error handling error-handling
Destination SDK API endpoints follow the general Experience Platform API error message principles. Refer to API status codes and request header errors in the Platform troubleshooting guide.
Next steps next-steps
After reading this document, you now know how to create a new destination server through the Destination SDK /authoring/destination-servers
API endpoint.
To learn more about what you can do with this endpoint, see the following articles:
To understand where this endpoint fits into the destination authoring process, see the following articles: