Page Comparison

...

The user will input the accessCode into the SafePaths app. An API request will be made against to this endpoint. The endpoint returns a boolean indicating whether or not the accessCode exists and is still activevalid.

• Endpoint: GET /access-code/valid/{accessCode} (https://pathcheck.atlassian.net/wiki/spaces/SA/pages/73924822/SPL+API+Specification+v1+For+MVP1#GET-%2Faccess-code%2Fvalid%2F%7BaccessCode%7D )

...

The user consents to the HA’s terms of service after the access code is confirmed to be valid. We record the user’s consent on the case record associated with the accessCode and set the access code to expire invalidate the accessCode record (set invalidatedAt timestamp) if the user did not consent to the terms of service.

...

User data (points of concern) are posted to the endpoint along with the access code accessCode. Validation on the code accessCode occurs once more and then we persist the provided user data.

...

• Return an appropriate error message to the client if the access code record has expired accessCode record is no longer valid (invalidatedAt timestamp is nil ) for any reason

• Return an appropriate error message to the client if the user has not consented to the HA’s terms of service

• Return an appropriate status code if there is a unexpired valid access code associated with the case and but no points of concern associated with the case (user has not uploaded data yet)

• Return all points of concern associated with the case if there are any

...