🚧

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.

🚧

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.