Discussions
Data Model
How can I get the data model?
More granular data dictionary for all endpoints
I am curious if the Humanity team is ever going to update/improve the data dictionaries for each endpoints response object? I feel this would be very valuable to the community ultimately because it will allow the end user to know more about the key:value pairs that are returned to them before ever actually hitting a Humanity API endpoint.
Long standing unpublished Shifts
We are curious to find out why we have so many old shift records that are still in an "unpublished" state that get returned from the GET SHIFTS api endpoint. We understand that at first a shift may appear "unpublished" because it was recently generated and will soon move to the "published" state by way of its timestamp changing, but we are curious about some shifts (from years ago in our case) that are still in an "unpublished" state and how we can make sense of them.
GET TimeClocks events with negative event types and out of order ID's/timestamps
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.
created and created_at for SHIFTS can have very different timestamps but seem to have the same meaning
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.
Mobile SDK
Do you provide an sdk for ios, android or react native?
Raising the API Limit
Hi there,
Does your API provide with some sort of socket that would allow us to watch for specific events?
Our client is using your software,
Very unreliable API
Thank you for the reply Aleksandar,
Very unreliable API
Your servers are down again and I no one is answering me.