Retrieve a destination publishing request
- Topics:
- Destinations
CREATED FOR:
- Admin
- User
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
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
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.
The following request will retrieve the list of publishing requests that you have submitted, based on IMS Org ID and sandbox configuration.
curl -X GET https://platform.adobe.io/data/core/activation/authoring/destinations/publish \
-H 'Authorization: Bearer {ACCESS_TOKEN}' \
-H 'x-gw-ims-org-id: {ORG_ID}' \
-H 'x-api-key: {API_KEY}' \
-H 'x-sandbox-name: {SANDBOX_NAME}'
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 configId
corresponds to the publish request for one destination.
{
"destinationId":"1230e5e4-4ab8-4655-ae1e-a6296b30f2ec",
"publishDetailsList":[
{
"configId":"ab41387c0-4772-4709-a3ce-6d5fee654520",
"allowedOrgs":[
"716543205DB85F7F0A495E5B@AdobeOrg"
],
"status":"TEST",
"destinationType":"DEV"
},
{
"configId":"cd568c67-f25e-47e4-b9a2-d79297a20b27",
"allowedOrgs":[
"*"
],
"status":"DEPRECATED",
"destinationType":"PUBLIC",
"publishedDate":1630525501009
},
{
"configId":"ef6f07154-09bc-4bee-8baf-828ea9c92fba",
"allowedOrgs":[
"*"
],
"status":"PUBLISHED",
"destinationType":"PUBLIC",
"publishedDate":1630531586002
}
]
}
destinationId
publishDetailsList.configId
publishDetailsList.allowedOrgs
Returns the Experience Platform organizations for which the destination is available.
- For
"destinationType": "PUBLIC"
, this parameter returns"*"
, which means that the destination is available for all Experience Platform organizations. - For
"destinationType": "DEV"
, this parameter returns the Organization ID of the organization which you used to author and test the destination.
publishDetailsList.status
TEST
, REVIEW
, APPROVED
, PUBLISHED
, DENIED
, REVOKED
, DEPRECATED
. Destinations with the value PUBLISHED
are live and can be used by Experience Platform customers.publishDetailsList.destinationType
DEV
and PUBLIC
. DEV
corresponds to the destination in your Experience Platform organization. PUBLIC
corresponds to the destination that you have submitted for publishing. Think of these two options in Git terms, where the DEV
version represents your local authoring branch and the PUBLIC
version represents the remote main branch.publishDetailsList.publishedDate
curl -X GET https://platform.adobe.io/data/core/activation/authoring/destinations/publish/{DESTINATION_ID} \
-H 'Authorization: Bearer {ACCESS_TOKEN}' \
-H 'x-gw-ims-org-id: {ORG_ID}' \
-H 'x-api-key: {API_KEY}' \
-H 'x-sandbox-name: {SANDBOX_NAME}'
{DESTINATION_ID}
If you passed a DESTINATION_ID
in the API call, the response returns HTTP status 200 with detailed information about the specified destination publish request.
{
"destinationId":"1230e5e4-4ab8-4655-ae1e-a6296b30f2ec",
"publishDetailsList":[
{
"configId":"123cs780-ce29-434f-921e-4ed6ec2a6c35",
"allowedOrgs": [
"*"
],
"status":"PUBLISHED",
"destinationType": "PUBLIC",
"publishedDate":"1630617746"
}
]
}
destinationId
publishDetailsList.configId
publishDetailsList.allowedOrgs
Returns the Experience Platform organizations for which the destination is available.
- For
"destinationType": "PUBLIC"
, this parameter returns"*"
, which means that the destination is available for all Experience Platform organizations. - For
"destinationType": "DEV"
, this parameter returns the Organization ID of the organization which you used to author and test the destination.
publishDetailsList.status
TEST
, REVIEW
, APPROVED
, PUBLISHED
, DENIED
, REVOKED
, DEPRECATED
. Destinations with the value PUBLISHED
are live and can be used by Experience Platform customers.publishDetailsList.destinationType
DEV
and PUBLIC
. DEV
corresponds to the destination in your Experience Platform organization. PUBLIC
corresponds to the destination that you have submitted for publishing. Think of these two options in Git terms, where the DEV
version represents your local authoring branch and the PUBLIC
version represents the remote main branch.publishDetailsList.publishedDate
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 Experience Platform troubleshooting guide.