Discussions

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.

Posted by [email protected] almost 3 years ago

Mobile SDK

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

Posted by jolly almost 3 years ago

Raising the API Limit

Hi there,

Posted by Angus Gastle almost 3 years ago

Does your API provide with some sort of socket that would allow us to watch for specific events?

Our client is using your software,

Posted by Sebastien Fock-Chow-Tho almost 3 years ago

Very unreliable API

Thank you for the reply Aleksandar,

Posted by Jolly almost 3 years ago

Very unreliable API

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

Posted by Jolly almost 3 years ago

Are your server down?

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

Posted by jolly almost 3 years ago

Error 404 on all the endpoints

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

Posted by certzo almost 3 years ago

Generating a non-expiring token

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

Posted by rolta almost 3 years ago

Loading Data from Amazon Connect for Demand Based Forcasting

Hi, can you please outline how humanity can ingest activitiy feeds e.g. queue/call activity metrics from Amazon Connect into humanity for demand based scheduling and forecasting. Is it via API and if so what is the appropriate methods, do you have a batch upload option

Posted by tilaga rungel almost 3 years ago