List view
Purpose of this milestone is the penultimate release of the Lead Safe API before Alliance integrates the API into their system.
Due by March 30, 2018•6/6 issues closed- Due by March 16, 2018•5/5 issues closed
The objective of the milestone is to define what will be returned in `risk_score` and `risk_score_notes` fields for the [API response](https://github.com/Chicago/lead-safe-api-docs/blob/master/docs/index.md#response).
Due by December 22, 2017•3/3 issues closedImplement mandatory security tokens which must be passed to the API before a result will be passed back to the client. For each transaction, the security token and timestamp for each transaction must be logged. Smoke testing should be conducted. This will be the first production release candidate for consideration.
Due by October 27, 2017•3/3 issues closedAdd robust error messages to clearly communicate any errors, issues, or if data is not yet available. All errors should be returned through HTTP Status Codes communicated in the API.
Due by September 29, 2017•6/6 issues closedPurpose of the v0.4.0 is to clean-up inconsistencies and establish naming patterns for the API to serve multiple health centers.
Due by September 15, 2017•3/3 issues closed