AJO custom action API request/response payload logs | Community
Skip to main content
Pradeep-Jaiswal
Pradeep-Jaiswal
Level 5
September 30, 2025
Solved

AJO custom action API request/response payload logs

  • September 30, 2025
  • 3 replies
  • 543 views

As part of QA validation, I want to randomly validate for some of the customer, what was the response received in the custom action of GET API call OR the payload that was sent as part of POST request. Doest AJO maintain these API request/response in any of the AJO native dataset ? or what's the alternative way QA person, who is not very technical person can validate the custom action API payload request/response value for a specific customer?

Best answer by Pradeep-Jaiswal

further investigation shows that log view can only be visible in test mode, for live journey the logs for custom action APIs are not part of AJO capabilities at the moment

3 replies

Mayank_Gandhi
Adobe Employee
Mayank_GandhiAdobe Employee
Adobe Employee
September 30, 2025

@pradeep-jaiswal Try  Test Mode (before publishing the journey), you can:

  1. Run the journey with test profiles.
  2. See detailed logs in the UI (request body, endpoint, status code, sometimes response content).
  3. Validate the structure and value of requests and responses in JSON format visually.

https://experienceleague.adobe.com/en/docs/journey-optimizer/using/orchestrate-journeys/create-journey/testing-the-journey

Pradeep-Jaiswal
Pradeep-JaiswalAuthor
Level 5
September 30, 2025

Th objectives is to validate the random records from already tested scenarios. Kind of audit. So manually validating the logs by executing the scenario is not a best fit situation here.

DavidKangni
Community Advisor
DavidKangniCommunity Advisor
Community Advisor
September 30, 2025

@pradeep-jaiswal 

try this https://experienceleague.adobe.com/en/docs/journey-optimizer/using/orchestrate-journeys/troubleshoot-journey/troubleshoot-custom-action

Adobe is planning to release Custom action monitoring and reporting but I don't know the timeline. This capability provides better visibility into journey health and execution, including lifecycle status and performance alerts. You can now quickly understand when, where, and why an anomalous situation is occurring in a custom action.

Thanks,

David

David Kangni
    Pradeep-Jaiswal
    Pradeep-JaiswalAuthorAccepted solution
    Level 5
    October 9, 2025

    further investigation shows that log view can only be visible in test mode, for live journey the logs for custom action APIs are not part of AJO capabilities at the moment

    Terms & ConditionsAccessibility statement

    Loading footer...