In a scripted decision node, you can access the request parameters or request headers, but not the request body from a POST call within a journey. While it is possible to retrieve the body when dealing with callbacks, this approach requires two API calls. However, in many cases, we use journeys as APIs.
Does anyone have a workaround or suggestion for this use case?
<< While it is possible to retrieve the body when dealing with callbacks, this approach requires two API calls. However, in many cases, we use journeys as APIs. >>
I have seen before this style of using AM journeys, and it actually gives me the chill. AM is not an application server, or API gateway. The purpose of a journey is to deliver a session to a user after gathering valid credentials, or reject by not providing the session at all. An API main purpose is likely not to authenticate the user, and if you’re not careful in its design, you could end up delivering a session to a user when it was not the intent - so potential breach. Additionally it’s kind of resource consuming for a REST API!