Notes
Our latest endpoint, for award billing schedules, is now available! We’re also halfway through creating another endpoint for award tasks that we anticipate will be available after the next sprint.
We’ve added some new filters for awards and award lines by user request. We’ve also added some new fields to awards that weren’t present in the original version. See the specifications for full details.
The FDM validation endpoint now handles whitespaces a little more gracefully, and the error messages that are returned are now formatted with quotes around the values passed in. This should make it easier to troubleshoot cases where you’ve accidentally passed in whitespace or an empty value instead of the ID of an FDM record.
We’ve nearly finished a new security feature that will allow us to scope the results returned from an endpoint by the company that they belong to. This will work in tandem with a previous feature to limit access to particular endpoints and will be an important part of how we secure the API for a variety of uses.
We’re looking into some possible refactors of our ETL process, using AWS Glue instead of our current solution of Python running in a Docker container. This has the potential to be easier to manage and will give us some new options for scheduling, like running our ETL process as soon as an update is received rather than on a predetermined schedule. We’ll have more on this in future sprint reviews.
API Changes
- New award billing schedules endpoint
- New filters for awards:
- company
- costCenter
- fund
- sponsorId
- New filters for award lines:
- revenueCategoryId
- fundId
- functionId
- New fields for awards:
- primeSponsorName
- primeSponsorId
- letterOfCreditId
- letterOfCreditDocumentId
- assistanceListingNumber
- assistanceListingDescription
- signedDate
- FDM validation errors now include single quotes around erroneous ID values