...
User data (points of concern) are posted to the endpoint along with the accessCode. Validation on the accessCode occurs once more and then we persist the provided data, as well as persisting the access code used for upload. The upload response contains a unique uploadId that can be subsequently be used to delete the uploaded data. The access code is invalidated upon success.
...
The SafePlaces frontend application will be polling GET calls to POST /cases/points (
| Status | ||||
|---|---|---|---|---|
|
accessCod and the caseId. Repeated calls may be made until a terminal status is reached:If the access code is invalid, an appropriate error status code is returned and the upload is aborted.
If the user declined the ToS, an appropriate error status code is returned
...
and the upload is aborted.
If upload has completed successfully, the endpoint returns the points of concern that were uploaded from the SafePaths app
...
for the given access token.
On the backend, the points will have been saved to the Private DB, and interaction with the Ingest/Upload DB is complete for this case.
Private WebUI Service
Read from Ingest/Upload DB
The frontend application then makes a call to POST /cases/points (
| Status | ||||
|---|---|---|---|---|
|
caseId. Private WebUI Service
Write to Private DB
Displaying Points for the Case
...