Retrieve a destination publishing request
platform.adobe.io/data/core/activation/authoring/destinations/publish
After you have configured and tested your destination, you can submit it to Adobe for review and publishing. Read Submit for review a destination authored in Destination SDK for all the other steps you must do as part of the destination submission process.
Use the publish destinations API endpoint to submit a publishing request when:
- As a Destination SDK partner, you want to make your productized destination available across all Experience Platform organizations for all Experience Platform customers to use;
- You make any updates to your configurations. Configuration updates are reflected in the destination only after you submit a new publishing request, which is approved by the Experience Platform team.
Getting started with destination publishing 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.
List destination publish requests retrieve-list
You can retrieve a list of all destinations submitted for publishing for your IMS Organization by making a GET request to the /authoring/destinations/publish
endpoint.
API format
Use the following API format to retrieve all publishing requests for your account.
GET /authoring/destinations/publish
Use the following API format to retrieve a specific publishing request, defined by the {DESTINATION_ID}
parameter.
GET /authoring/destinations/publish/{DESTINATION_ID}
Request
The following two requests retrieve all publishing requests for your IMS Organization, or a specific publishing request, depending on whether you pass the DESTINATION_ID
parameter in the request.
Select each tab below to view the corresponding payload.
accordion | ||
---|---|---|
Request | ||
The following request will retrieve the list of publishing requests that you have submitted, based on IMS Org ID and sandbox configuration.
|
accordion | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Response | ||||||||||||||||||||||||||
The following response returns HTTP status 200 with a list of all destinations submitted for publishing that you have access to, based on the IMS Organization ID and sandbox name that you used. One
|
accordion | ||||||||
---|---|---|---|---|---|---|---|---|
Request | ||||||||
|
accordion | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Response | ||||||||||||||||||||||||||
If you passed a
|
API 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.