Breaking API Change – Action Required

We’re phasing out support for a legacy syntax used in filtering GET requests to our API. This change is part of a broader migration project to improve API performance, security, and maintainability.

When is this happening?

Support for the legacy format will end in early 2026, following the completion of our migration project. This gives you the remainder of 2025 to update your API calls and avoid any disruption.

We’ll continue to send reminders and provide an exact cutoff date as we get closer to completing the migration.

What’s changing?

We will no longer support the parameter[key]=value syntax for filtering in GET requests. Instead, you'll need to use dot notation in your query parameters.

Before (unsupported):

model[employeeId]=123

filter[toDate]=2025-06-29
‍

After (supported):

model.employeeId=123

filter.toDate=2025-06-29

What do you need to do?

If you use our Payroll API, we recommend reviewing your current integrations and updating any filtering query parameters to use dot notation as soon as possible.

What happens if you don’t update?

Once support for the old syntax ends, GET requests using the legacy format will fail. This may cause API integrations to break and disrupt any dependent systems or services.

‍