Sprint review notes: Sprint 92
Notes
Welcome to the Locations API blog! Here we’ll post updates and notifications related to the Locations API. Mostly this will be summaries of our biweekly sprint reviews, but there will be other posts as needed.
The Locations API is developed and maintained by the same team that built the Finance API. During our sprint reviews, we talk about whatever the team has been working on for the last two weeks. Depending on the sprint, this might include work on the Locations API, the Finance API, or both. As of this post, anything that’s only relevant to the Locations API will be posted here, and anything only relevant to the Finance API will be posted on its site.
If you’re looking for older updates, check the Release Notes section of the Finance API website. Our recent work on the Locations API is documented there.
This sprint we made a number of fixes and improvements to the Locations API:
- Corrected the base URL for pagination links
- Errors will now be served in JSON format instead of the default HTML
- Filters are now insensitive to case and diacritical marks. Filtering for “Madison” will return the same results as “màDIsöN”.
- ETL has been scheduled and will run in the wee hours every day. You can expect new data to be present in the API by 4am.
We also added a bunch of static checks to our Continuous Integration pipeline to ensure code quality stays high.
API Changes
- Pagination links now have the correct base URL
- Error responses are in JSON instead of HTML
- Filters are no longer sensitive to capitalization or diacritical marks