Notes

This sprint we worked on our internal infrastructure for supporting multiple addresses per location. We’re refactoring parts of our code to allow for this possible expansion in the future. We rewrote parts of our internal code representation and modified our ETL process to be capable of loading multiple addresses.

We made some improvements to how server errors are handled. These should be rare when the API goes into public use, but if one of your requests triggers a server error (HTTP status code 500), you’ll see a unique request ID number. If the problem persists, contact the Locations API team and include the request ID. We’ll be able to use that to track down the detailed logs and find out exactly what went wrong.

We’ve also set up the API to send us notifications in Teams whenever someone triggers a server error, so even if users don’t report the issue we’ll be aware of it.

We completed implementation of a new way to deliver large files of results. Whenever you request a response in CSV format, your result will be sent to you via a redirect to a presigned AWS S3 link. Follow the redirect and your file will be downloaded. These links only work for 15 minutes from the time they were generated, so if you need to retrieve the results again later, you’ll need to send a new request.

API changes

• Server error notifications are now delivered in JSON format instead of HTML
• Server error notifications include a unique request ID that can be used for troubleshooting
• Requests for CSV data are now delivered via a 302 Redirect to a link on AWS S3. You may need to configure your API client to follow these redirects.

Recording

ASP API Sprint 93 Review