Hi thanks for the reply, and yes we have looked at those docs and even played around with the live-events. The issue we are most likely will run into is just the exceptional amount of UserUpdateEvent&...

I totally agree with you, the problem is that Canvas IS the only source of truth for a lot if not all clients.There is no way of only syncing change logs and as so we end up being forced into syncing ...

Currently we indeed sync only every 6 hours, yet for this new use-case this is not sufficient.As "near realtime" goes in our definition.. that would be max 60 seconds, but rather 10 then 20 se...

We are using the Canvas REST API to synchronize users into our application.Every 6 hours we are requesting: - all users- all coursers- all section- all enrollmentsfor 129 different schools/clients. We...

Hi, thanks for your reply!I am looking at the docs and it might be wishful-thinking but: // The beginning date for submissions. Max time range is 2 weeks. "start_at": "2012-07-13T10:55...

Hi thanks for the reply, and yes we have looked at those docs and even played around with the live-events. The issue we are most likely will run into is just the exceptional amount of UserUpdateEvent&...

Hi, thanks for your reply!I am looking at the docs and it might be wishful-thinking but: // The beginning date for submissions. Max time range is 2 weeks. "start_at": "2012-07-13T10:55...

I totally agree with you, the problem is that Canvas IS the only source of truth for a lot if not all clients.There is no way of only syncing change logs and as so we end up being forced into syncing ...

Yes, I have been thinking about that too, the problem is that most mutations are made within Canvas itself and with that forces itself to be the source of truth. As far as I understand they are not us...

Currently we indeed sync only every 6 hours, yet for this new use-case this is not sufficient.As "near realtime" goes in our definition.. that would be max 60 seconds, but rather 10 then 20 se...