Hi @sarav_prakash  Yes, you must store the last position to fetch the next batch of events. However, we recommend looking at the `link` response headers  with rel="next" and persisting that URL to fetch the next batch of events.See: https://developer.adobe.com/events/docs/guides/api/journaling_api/#...

Hi @JoelSa6 , could you confirm a few things -  1. You are using the correct account to sign in 2. Once you are on the Dev Console can you click on the org switcher (on the top right) and see if you have access to the org for which you received the email?  ThanksManik 

Hi @alejandroluzuriaga, thanks for a detailed write-up. I cannot help as the question is very specific to the product/API you are using. Instead, I'd recommend you raise a ticket with Adobe support through your regular channels to get an answer.  Meanwhile, you can keep the question open to see if s...

@Siva5CB9for our developers to triage the issue, I'd ask you to open a support ticket with Adobe. 

Yep, step #3 is likely failing because your splunk is not accessible to public internet. Can you try to cURL into it from a different network? If you are on your company network you might still be able to access your Splunk via cURL but not the public internet.  

Hi @JosephKa2  Ultimately your integration needs to be updated to use OAuth Server-to-Server credentials. There are two ways to get there -  Route#1 Directly migrate to OAuth Server-to-Server credentials in the next 30 days This is a viable route and will not involve creating a new certificate pair....

Hi @rileyzo - all information can on the migration can be found on these doc pages below -  1. https://developer.adobe.com/developer-console/docs/guides/authentication/ServerToServerAuthentication/migration/2. https://developer.adobe.com/developer-console/docs/guides/authentication/ServerToServerAut...

Hi, @Siva5CB9  the error is coming from your Splunk. The connection is timing out. Have you made sure your splunk is accessible on the public internet so that we can forward logs to it? 

Let me see what I can do.  

Hi @GrantWa3 - I recommend you contact Customer Support through your existing channels. They should be able to provide a more authoritative answer.