Hi @drewglass1,You can intercept the original validation URL if you own the webhook server (by simpy logging all requests). We purposefully obfuscate the validation URL in debug tracing tab for security reasons.Hope this helps.

Hi @humberto_munoz, would it be possible to share the logs that you are getting for the NPE?I am assuming the steps you mentioned, have been performed for both local and production environments in the exact same manner (especially setting up your workspace in the Developer Console, and as OSGI confi...

Hi @navink386520: The Journaling API documentation that you are referring to contains an example where the original event has a timestamp field. We simply wrap the original event payload and deliver it as is.In your case, the AEP data ingestion events may not have a time-stamp field and that's why y...

What exactly is your use-case?

This is not possible right now with the already published package that we have (see https://www.adobe.io/apis/experienceplatform/events/docs.html#!adobedocs/adobeio-events/master/aem/aem_skyline_install.md). One thing that you could do is extend the package as per your needs.Having said that, we are...

When I posted my debug results, I included a snapshot of both the request and response tabs (see below for a better image). That's where you see the difference of headers. But looking at your traces, it seems that the events are being delivered just fine. Regarding the slack integration, I did not t...

Great! Thanks for confirming.

Thanks for sending the details @jgrubbs. We did have an issue at our end in processing triggers. The problem is now resolved. Could you please confirm if it's fixed at your end also?

There is definitely no latency at our side for the Journaling API, but to be doubly sure, could you help us with the IMS organization id and the journaling endpoint for debugging? I can go through our Splunk logs and verify if things are working correctly.

I am not sure what's going wrong at your end. Could you please check what you are getting in the Debug Tracing tab of your console integration (created in step 0). The tutorial has been coded to respond with a simple "pong" message for every event delivered to the webhook, so I don't see any issue h...