Discussions

The issue we are facing is with negative event types and out of order ID’s/Timestamps. We currently do not understand why there would ever be a negative event type and need to understand it deeper so we can make proper sense of our data. As for the out of order event ID’s and timestamps, on the event data array, we’d assume the id’s would be in sequential order, but they jump around a bit and the timestamps follow suit. Our initial assumption is that the order of ID’s/Timestamps should be sequential for any given timeclock_id, so we need to know more about what it means when they are out of order.

We rely heavily on your SHIFTS GET endpoint to be the source for one of our ETL processes. We are having issues with the created_at property being much newer than the created property timestamp. The assumption is that these should be the same value no matter what, but as we go back historically (specifically starting on 2018-06-01) the created_at properties timestamp is always '2018-06-02 16:05:22.000' and the created properties timestamp can be as much as two years earlier.

Do you provide an sdk for ios, android or react native?

Hi there,

Our client is using your software,

Thank you for the reply Aleksandar,

Your servers are down again and I no one is answering me.

I can't seem to be able to reach your API. Are the servers down?

I'm receiving 404 errors on all the endpoints. How do I fix this?

Is there a way to generate a non-expiring token? It's a bit tedious to refresh the token