Discussions

Hello, I was trying to pull all leaves, pending and not pending, and it seems like i'm only getting approved leaves. Unless every request has an 'approved_on' value assigned regardless of pending or not. I've already tried the different parameters, "requested, all_requested, upcoming, and manager" but they all seem to return the same data, and looking at the Humanity app itself I see pending requests that I can't find in the data provided by the API.

1. What is the unit of expiry_at for Access Token Creation via API expiry time? is it seconds? 2. Can access token expiry be longer? Like 14 days just like created via dashboard?

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?

Using PUT Employee and saw removeschedule, however we are not utilizing schedules. Is there a way to remove a user from any/all assigned shifts when they are disabled/deactivated through the API?

We can't find any proper API the will return Total Cost of the week Lite this report showing Payroll -> Scheduled Hours ->ThisWeek-> Location = Wilsonville Total Cost

I have been trying to log on to my Humanity account but I always get a "403 Error" or a "could not get a response from server" message. I tried using different laptops, and even uninstalled-then-reinstalled the mobile app on my phone, but still the same issue. I urgently need to access my account. Please help. Thank you!

The tokens returned by the oauth endpoint are not working. Here's my example curl request: Oauth request: curl --location 'https://www.humanity.com/oauth2/token.php' \ --header 'Content-Type: application/x-www-form-urlencoded' \ --data-urlencode 'client_id=ac17a5e7440f7bea3fcfaae5b9054200eb269aa7' \ --data-urlencode 'client_secret=ae63a59372d4f10e2cc41c3164f887bae03c3442' \ --data-urlencode 'grant_type=password' \ --data-urlencode '[email protected]' \ --data-urlencode 'password=************' Response: {"access_token":"8787ef2fc6732f3f10afd7fbabf50d55c79e6dd0","expires_in":3600,"token_type":"Bearer","scope":null,"refresh_token":"33997ce5179f89c0f5c455fa3a77aee8a931f17d"} Request to /shifts using the access_token from the above response: curl --location "https://www.humanity.com/api/v2/shifts?access_token=8787ef2fc6732f3f10afd7fbabf50d55c79e6dd0&end_date=2023-03-04&start_date=2023-03-03 Response: {"status":20,"data":"Incorrect Permissions - You don't have the proper permissions to access this","error":"This account is not activated.","token":"8787ef2fc6732f3f10afd7fbabf50d55c79e6dd0"}

Is there a way to use the API to track sub-shift time blocks? I believe tasks are the way to handle this, but I did not see an API reference to tasks.

There is a lot of extraneous data returned for many of the API endpoints. It would be great if there was something like a `fields` parameter to scope the specific fields returned. Ex: If I need to programmatically pull the shifts for users with a specific email domain, I first need to query all users. Each user contains 44 individual keys/names many of which are empty. If I have 100 users, I have to parse 4,312 keypairs that I do not need. Then, while iterating shifts, I need to parse 42 individual keys/names. I may only be interested in a handful of these fields across thousands of records, meaning there are tens of thousands of unnecessary keypairs being returned.

Hi, I am looking for a solution via API to check/uncheck the option under the setting for "Restrict Employees from adding, editing, and deleting their unavailability" Can this action be implemented via API call? Thanks