Description
Adobe Journey Optimizer (AJO) currently provides a "Copy Technical Details" option in the UI that exposes key configuration parameters of a journey in JSON format. This includes important fields such as throttlingRatePerSec, entryConditions, and activity configuration. However, this JSON is only accessible manually via the user interface, and not available through any public API.
Why is this feature important to you
We are building governance and automation processes to validate AJO journeys before and after publishing. One of our goals is to enforce configuration standards, such as ensuring that the throttlingRatePerSec is always set to a specific value (e.g., 500).
Having API access to this technical JSON would allow us to implement:
Automated pre-publication approval workflows
Regular audits of existing journeys
CI/CD-like governance for journey configuration
Without programmatic access, we are forced to rely on manual inspection, which is time-consuming and error-prone.
How would you like the feature to work
Ideally, Adobe would expose a public API endpoint (via Adobe I/O or Journey API) that returns the same JSON currently available in "Copy Technical Details".
This endpoint should return a complete JSON structure with all configuration fields exposed in the UI technical details.
Current Behaviour
Currently, the only way to access the technical details JSON is through the "Copy Technical Details" button in the AJO interface or check via UI. This action must be done manually, and there is no documented or supported API to retrieve this configuration programmatically. As a result, automation of journey validation is not possible with the current setup.
Thanks!
Lucas Sanches Andrade
Digital Analyst @Banco Bmg
