🚧

As of July 31st, 2024, we will be discontinuing the Read my tasks endpoint

This change is part of our ongoing efforts to enhance security and streamline our API authentication methods. It may require some adjustments on your end, but the good news is that we have already prepared an alternative endpoint that can replace the functionality of the discontinued endpoint: Read tasks of a specific employee. This endpoint will provide you with similar functionality to the one you are currently using.

What do you need to do?

We recommend updating your code to use this endpoint before the discontinuation date to avoid any disruption in your services. If you have any questions or need further assistance, please contact our support team.

We've enhanced our document management capabilities with new endpoints. Previously, you could manage documents in either an employee's confidential or shared folders. Now, you have the flexibility to manage documents across all of an employee's folders.

The new endpoints include:

• Upload a document to an employee's custom folder
• Upload a file to an employee's custom folder
• Delete a specific document from an employee's custom folder

These new features provide more control and flexibility in managing employee documents. If you have any questions or need further assistance, please contact our support team.

❗️

Final Notice: API Access Tokens Shutdown by April 30, 2025

The "API Access Token" authentication method will be completly shut off by April 31, 2025.

Companies using this legacy method should transition to the Service User method before April 30. From this date, API integrations using API Access Tokens will stop working. Any system or process that relies on API Access Tokens will fail, potentially causing disruptions.

Follow the instructions below to transition to the Service User authentication method.

🚧

Effective October 31, 2024 the "API Access Token" authentication method will be discontinued.

Starting October 31, 2024, we will exclusively support the API Service Users method for API authentication. This change is a step towards strengthening security measures and ensuring a more robust and reliable service for all our users.

What do you need to do?

• By June 15, 2024: Ensure you do not create any new API Tokens, as it will no longer be possible. Please incorporate this change into your processes. You can continue to manage existing tokens until October 31, 2024.
• By October 31, 2024: Transition fully to the API Service Users method for API authentication.

Please ensure you update your systems and processes accordingly. If you have any questions or need further assistance, feel free to contact our support team.

🚧

As of July 31st, 2024, we will be discontinuing the Read Avatar for Logged-in User endpoint.

This change is part of our ongoing efforts to enhance security and streamline our API authentication methods. While this may require some adjustments on your end, the good news is that we have already prepared alternative endpoints that can replace the functionality of the discontinued endpoint: Read Avatar for an Employee ID and Read Avatar for an Employee Email.

What Do I Need to Do?

By July 31st, 2024: Update your integration to use the alternative endpoints:

• Read Avatar for an Employee ID
• Read Avatar for an Employee Email

Updating your systems to use these endpoints before the discontinuation date will help avoid any disruption in your services.

If you have any questions or need further assistance, please contact our support team.

❗️

Final Notice: API Get Endpoint Shutdown by April 30, 2025

The Get endpoints listed below will be completely shut off by April 30, 2025.

If your organization is still using the deprecated endpoints, action is required to prevent disruptions. Any processes relying on these endpoints will stop working, potentially impacting your operations. Follow the instructions below to migrate to the new endpoints.

🚧

The following endpoints will be deprecated on March 31, 2024:

'Read All Company Employees' and 'Read Company Employee by ID'. Additionally, as of April 2, 2024, the rate limits on these endpoints will be reduced from 100 to 70.

As part of our ongoing efforts to enhance performance, stability, and security, we're updating our APIs. We've introduced a new Search API to replace the two GET endpoints for reading all company employees and employees by ID.

The new Search API allows you to retrieve specific employee data and is designed for controlled access by API Service Users only, offering enhanced security and stability.

What Do I Need to Do?

• Familiarize yourself: Review the new Search API documentation.
• Update implementations: Review and update your API implementations to use the new endpoints.
• Test and transition: Thoroughly test the new API in your environment and transition to it in your production systems.

Benefits:

• Faster performance: Quicker responses with optimized speed.
• Enhanced stability: Improved service reliability.
• Balanced resource use: Fair allocation and prevention of misuse.

Please ensure you update your integrations to avoid disruptions. If you have any questions or need further assistance, please contact our support team.