[justin_oaks]

Wow, that's an awful design. It's even harder to implement that than to leave it stateless and require the client to pass in a date range.

[slver]

Think about it like a message queue. You can't keep things stateless and serve old data forever, or you have a queue that grows forever.

What you can do however is have an explicit "ack" for data being received and stored, before it's discarded. And apparently that API didn't.