Notes
This sprint we added expenditure treatments to Internal Service Deliveries (ISDs). Most ISDs won’t have this value set, but for those where it is, you can now get this value from the API. We also did some cleanup on the tax codes endpoint, mostly making the types in the specification better match the way they work in the API.
We fixed a bug related to filters on true/false values. Previously, you could send a filter like ?filter[active]=1234 and you’d get results back. Now, trying to use any value other than true and false in one of those filters will result in an error status code and explanatory message.
We’re currently working with EAP to finalize the details of how we’ll connect to their resources to provide API access to journal entries. We won’t have a working endpoint to show for a couple of sprints, but it’s on its way and isn’t facing any current blockers.
We’re currently taking a pass through the user-facing parts of the API to standardize our naming conventions. We currently have a mix of snake case (which_looks_like_this) and camel case (whichLooksLikeThis). We’re going to use camel case everywhere. This will mean that the names of attributes and filters will change, so this may require some adjustments to your integrations. We’ll publish a full guide to everything that needs to change when we roll out the new names.
We also did some internal security work to update some of the Docker images we’re using behind the scenes.
API changes
- ISDs now have expenditure treatments
- You’ll now get an error if you try apply a filter to a boolean field (true/false) using an invalid value (anything other than true or false)