Discussions

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.

We have support staff that cover multiple locations at the same time. It seems like
if an employee is scheduled at the same time at multiple location or positions, the shift endpoint with mode=oncall randomly returns only one shift.

I've been connecting to the api all morning with the humanity sdk for php, but about 2 hours ago I started getting a message that the login failed. This is happening in dev and in production. The code in production hasn't been changed for at least 4 months.

I am learning that several of the APIs do not return data if the position has been deleted; however, once it is reactivated, I can retrieve it. For the following API:

We need an API to allow our employee to login to Humanity .and this API should give me the employee id to be able later to get employee shifts

I used to go to shiftplanning.com/api/explorer to test an API.

It looks like you used swagger to generate your API, do you expose the file so that I can generate a client for the API?

I'm attempting to use PUT Shift to repeat a shift that I've created using POST Shift and GET Publish. The intention is to have it repeat all weekdays from the date of the original shift to a specified ending date.