Missing API for Datastreams | Community
Skip to main content
yuhuisg
Community Advisor
yuhuisgCommunity Advisor
Community Advisor
July 1, 2022
Solved

Missing API for Datastreams

  • July 1, 2022
  • 3 replies
  • 2440 views

I'm looking at AEP's API docs to see if there's a way to automate an initial setup for Web SDK tracking (i.e. automate the steps described at https://experienceleague.adobe.com/docs/platform-learn/implement-web-sdk/overview.html?lang=en).But the biggest obstacle is automating Datastreams. It looks like there is no API for Datastreams, from what I can see at https://developer.adobe.com/experience-platform-apis/. Am I correct: do all of the Web SDK setup steps have corresponding APIs that can be used except Datastreams?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Stewart_Schilling

There is an API.  I've used it.  I'm not sure if it has public docs or not. 

 

As with pretty much everything else, the Data Stream management functionality was developed in an API-first fashion.  Remember that "DataStreams" were originally called "EdgeConfigs". 

The API endpoints operate on https://edge.adobe.io and pretty much follow REST protocols, so you can figure out how to do what you want to do from the outside. 

 

What you want to do is to exercise the Data Streams UI manually while paying close attention to the calls made to https://edge.adobe.io in the network tab.  From the network tab you can see what methods (GET/POST/PUT/PATCH) are used, what request headers are sent, and how request bodies need to be formed. 

 

Remember also, that DataStream configuration is done in "Tags" (Adobe Launch), so when you get around to creating an Adobe IO project you'll want to include the "Experience Platform Launch API" service so that your process will have the permissions that it needs to interact with (CRUD) DataStreams.

3 replies

Manoj_Kumar
Community Advisor
Manoj_KumarCommunity Advisor
Community Advisor
July 1, 2022

Hello @yuhuisg 

You can take advantage of Adobe launch to collect data via AEP web SDK.

 

 As explained in the link below you will have to collect data in the datalayer and then map those variables to XDM schema.

https://experienceleague.adobe.com/docs/platform-learn/implement-web-sdk/tags-configuration/create-data-elements.html?lang=en#map-data-elements-to-xdm-objects

 

You will have to make rules to let SDK know when you want to collect data and what data you want to collect.

 

 

Manoj  | https://themartech.pro
    yuhuisg
    Community Advisor
    yuhuisgCommunity AdvisorAuthor
    Community Advisor
    July 1, 2022

    @_manoj_kumar_ yes, I'm familiar with that process.

    I'm asking about automating the process, in particular, that there doesn't appear to be an API for Datastreams, and as a result, the process cannot be automated completely.

      M
      mdonke
      Level 4
      July 1, 2022

      I hear you!

      I also couldn't find the API for that.

      But I believe there is one. In context of AEP trainings there is/was some automation in place.


      Screenshot below looks like automated provisioning is possible:

       

      Stewart_Schilling
      Community Advisor
      Stewart_SchillingCommunity AdvisorAccepted solution
      Community Advisor
      July 12, 2022

      There is an API.  I've used it.  I'm not sure if it has public docs or not. 

       

      As with pretty much everything else, the Data Stream management functionality was developed in an API-first fashion.  Remember that "DataStreams" were originally called "EdgeConfigs". 

      The API endpoints operate on https://edge.adobe.io and pretty much follow REST protocols, so you can figure out how to do what you want to do from the outside. 

       

      What you want to do is to exercise the Data Streams UI manually while paying close attention to the calls made to https://edge.adobe.io in the network tab.  From the network tab you can see what methods (GET/POST/PUT/PATCH) are used, what request headers are sent, and how request bodies need to be formed. 

       

      Remember also, that DataStream configuration is done in "Tags" (Adobe Launch), so when you get around to creating an Adobe IO project you'll want to include the "Experience Platform Launch API" service so that your process will have the permissions that it needs to interact with (CRUD) DataStreams.

        yuhuisg
        Community Advisor
        yuhuisgCommunity AdvisorAuthor
        Community Advisor
        July 13, 2022

        Thanks for sharing this. So it's not really a public API in the sense that it has not been made publicly aware nor does it come with any up-to-date documentation.

        I generally shy away from such usage, because things could still change. I'll wait and see if Adobe releases a proper public Datastreams API.

        Terms & ConditionsAccessibility statement

        Loading footer...