Discussions

We are currently doing an integration into Humanity but it appears that the publish API is temperamental. At times it does it properly so when you go into the UI the Publish button is greyed out and at other times it has the "Update & Publish" button clickable. This is causing a lot of major issues downstream. Any advice on how to deal with this issue?

I'm trying to generate a token through powershell and so far - I'm getting the status code of 200 no matter what I type in.

The error status received in APIs Will that be consistent?

Hello,

Hello,

Hiya,

When adding an employee to a shift through the API with PUT /shifts/id endpoint, using the add parameter, is the shift automatically published? It does not seem to be published.

We recently made changes to our allowable cipher list. Now, after years of flawless integration, we can no longer access your API service.

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.