The versions on this page represent breaking changes that we have made to our API since January 2021. The definition of a breaking change is one that causes some code that was written against a prior version of our API to break in the new version. Breaking changes are most commonly caused by either removing or renaming existing fields in the API, or by making a field required that was previously not required. Adding new endpoints or new fields to existing endpoints do not constitute breaking changes, because they do not break our partners' preexisting code. For more information on how to use a specific version of our API, please see our page on Versioning.
We release new code, functionality, tests, and other features to the Check API many times per day. However, we do our best in our power to minimize the number of breaking changes that we release to Check's APIs. This is because we want to avoid forcing our customers to change their code to benefit from new features that we've launched to our system. We publish all new changes and features that we release to our product on our Changelog.
- The datatype of the
approval_deadlinefield returned on a payroll is now
- When creating a post-tax deduction with a
child_support, the related employee must now have a
- JSON structure of payroll item warnings has been updated to provide more detail and support additional deduction types
reimbursementsfor payroll items is now required to be greater than $0.00
- JSON structure and design of paystub endpoint has been updated to return a breakdown of current earnings in the period
phoneis now a required field on company
- Introduced API versioning