My tests show that the timestamp works when sent in San Francisco's time zone, not working with utc, and not with the network's time zone. Could not find any documentation on this. Is it true that the parameter works in SF timezone only, or am I missing something, maybe a header parameter?
Let me be up front and say I think this API has had some bugs in it. I find it a painfull API to work with.
From my personal experience if you are dealing with "real time" events you need to wait up to 90s after the time when the time occurred before the snapshot API will correctly work.
Sometimes it will work after 10s. Sometimes 60s. Sometimes 90s. Sometimes it never works.
Personally I use a loop. I tend to wait 30s before attempting to call the API. I then sit in a loop and try maybe 10 times calling the API with a 30s delay in between the calls. After that about 5 minutes has passed and if you haven't gotten it by then you're never going to get it.
The latest firmware, V4, specifically mentions having improved this issue. However I have not been brave enough to upgrade to V4 yet. The upgrade is one way - you can not downgrade. And V4 is beta.
Thank you for your reply. I too was getting inconsistent behavior when trying to get real time snapshot, so instead I switched to getting the snapshot 5 mins before current time. That is OK for my requirements.
The thing I noticed with that method is, as I need to provide a timestamp to get the snapshot at a specific time, is that the API accepts timestamp parameter in Los Angeles timezone.