System Log API - Polling requests

Thanks for pointing it out - as i looked at the details i recalled that i’d noticed this before.

I had a brief convo with the team responsible - they agreed to take a closer look at the behavior so they can address it or just clarify in the docs. I’ll try and relay the response here.

That said - for the use case you mention (and almost any other i can think of) the best thing to do is to retain the next or the self link from the link headers returned from Okta and use those as the starting point of your subsequent interval polling.

Use the next link if you have the ability to evaluate the number of results you’ve just received versus the limit you’ve specified. If the number of results you receive is less than you asked for you can be rather certain the next link will be an empty response.

Use the self link if you just want to wait until you get an empty page.

-Matt