Hi @rgala, If you are trying the below consent request, make sure to do the following: Replace <api_key_from_console> with your own client-id.Make sure your client-id has the requested scopes. Notice how the consent request has the AdobeID, openid and creative_sdk scopes. One trick is to add the "Cr...

Hi @ashok-tech, This community is specifically for questions related to Adobe I/O Events. Your question seems relevant for the AEM community. Could you please ask your question there.

Hi @nagendrabattula5641258, This community is specifically for questions related to Adobe I/O Events. Your question does not seem to be relevant here. Please try asking in the AEM community.

Hi @bartek_887: I believe this question is more relevant for the app builder community.Can you please reach out there and see if that helps!

Hi @nuzil,I noticed that you are using the https://io-webhook.herokuapp.com/ as the webhook server. There is a known bug in this server where it's only able to display payloads when the content type is application/json.If you created this integration using developer console, you should be able to vi...

@zeiss_hs I am not sure if I fully understand your question, but let me take a stab at it.If you have Adobe I/O Runtime enabled in your org, then you can deploy a Runtime action that essentially does the same modification. You can then use Runtime Action as a Webhook against your events integration ...

Hi @zeiss_hs,You cannot directly use a Slack webook with Adobe I/O Events, because of the same constraint you mentioned. You will need a webhook to proxy your event payload to Slack in a compatible format. This can be achieved by a simple Adobe I/O Runtime action (or any other serverless function). ...

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...