Integrate adobe launch and Bitbucket

[reddy_y-11]

Hello Everyone,

Planning to integrate adobe launch and Bitbucket. Lastest published code from Adobe Launch to push into Bitbucket repository to keep code recorded for future reference.

While i reaching found Reactor API. https://experienceleague.adobe.com/docs/experience-platform/tags/api/overview.html?lang=en

I got few questions -

• If we want to go with Reactor API should we impliment AEP or webSDK?
• Can we do it without implimenting AEP or webSDK?
• Can we integrate adobe launch and Bitbucket?

Need your guidance on how we can impliment and automate the process and send the data to Bitbucket from Adobe Launch. Any suggestions and steps would be appreciated.

[bjoern__koth]

Hi @reddy_y-11 

the API has nothing to do with AEP nor WebSDK. You will just get access to individual Launch properties.

there used to be a Reactor Sync repository which I think was no longer maintained and still uses JWT tokens and not Oauth

https://github.com/adobe/reactor-sync

[reddy_y-11]

Thank you! @bjoern__koth 

Do we required any Licence for adobe?

[bjoern__koth]

No, API access should suffice 

[reddy_y-11]

What is the difference between Experience Platform Launch API and Experience Platform API ?

[bjoern__koth]

It depends on what you want to achieve. Both, Adobe Launch and Experience Platform are accessible through the API, but they are two fundamentally different things.

• Launch is the Tag Management System, how you get data into the Experience Platform, play out tags on your website, etc. and is free. This is what you want as I understand 
• Experience Platform gives you access to the whole data services of the experience platform to ingest data and profiles, and many other things. This is a whole different thing 

[reddy_y-11]

Thanks! for the reply.

Do we have any other options besides the Reactor API?

[bjoern__koth]

You can also manually download the whole Launch property as zip file. This is intended for self-hosting your files and will require you to specify a path where the files would be uploaded later.

But the rules and data elements should still be in there. surely not as fine granular as the API

https://experienceleague.adobe.com/en/docs/experience-platform/tags/publish/self-hosting-libraries