References

• MVP1: App to SPL Flow

• SafePaths <-> SafePlaces Data Flow Overview

• Open API 3.0 version on Apiary

• Hashing of GPS points - Design | Safe Places Publishing of Data

• SPL Token Exchange

• Design for MVP1 HA JSON Changes

• Public vs. Private Instances of SafePlaces APIarchived

• SafePlaces API Architecture

• SPL Data States (For MVP1)

• SPL UI Protype (Figma)

Public endpoints

IMPLEMENTED: GET /access-code/valid

Determines whether an access code is valid and if it can be used to perform an /upload API call.

See SPL Token ExchangeMVP1: App to SPL Flow

Parameters

No parameters

Request body

Responses

IMPLEMENTED: POST /consent

Logs user consent to health authority’s terms of service. Invalidates the accessCode that is passed in the payload if consent is false.

See MVP1: App to SPL Flow

Parameters

No parameters

Request body

Responses

IMPLEMENTED: POST /upload

Accepts SAFE PATHS data upload from the user. Access code sent in body must match an access code created in a POST /access-code call. The uploadId returned may be used by clients to purge data from this upload at a later time.

see Design for MVP1 HA JSON Changes SPL Token ExchangeMVP1: App to SPL Flow

Parameters

No parameters

Request body

application/json

• Example Value

Responses

Private endpoints

IMPLEMENTED: POST /login

Authenticates the user and responds with a JWT that can be used to access protected endpoints.

See SPL Token Exchange.

Parameters

No parameters

Request body

application/json

• Example Value

Responses

Confirmed: POST /access-code

Returns a new access code that clients can use to upload data via the public endpoints above. The code should remain valid for 1 hour.

See SPL Token Exchange.

Parameters

No parameters

Request body

No body

Responses

IMPLEMENTED: GET /organization

Returns information about the organization associated with the requesting user.

Parameters

No parameters

Request body

No body

Responses

IMPLEMENTED: GET /organization/configuration

Returns the configuration of the organization associated with the requesting user.

See SPL UI Protype (Figma)

Parameters

No parameters

Request body

No Body

Responses

IMPLEMENTED: PUT /organization/configuration

Updates the configuration of the organization.

See SPL UI Protype (Figma)

Parameters

No parameters

Request body

application/JSON

• Example Value

Responses

IMPLEMENTED: GET /organization/cases

Gets a list of case records for the organization

See SPL UI Protype (Figma), SPL Data States (For MVP1)

Parameters

No parameters

Request body

No body

Responses

IMPLEMENTED: POST /organization/case

Creates a new case, and associates it with the organization of logged in user.

See MVP1: App to SPL Flow, SPL Data States (For MVP1)

Parameters

No parameters

Request body

No parameters

Responses

IMPLEMENTED: PUT /case

Updates a case (currently only supports updating of case’s extern id)/

Parameters

No parameters

Request body

application/JSON

• Example Value

Responses

IMPLEMENTED: DELETE /organization/case

Delete case record

See SPL UI Protype (Figma)

Parameters

No parameters

Request body

application/JSON

• Example Value

Responses

IMPLEMENTED: GET /case/points

Returns all points of concern for the provided case.

See SPL UI Protype (Figma)

Parameters

No parameters

Request body

application/JSON

• Example Value

Responses

Confirmed: POST /case/points

Associates the results of a previous upload with a case. accessCode should match a code returned from POST /access-code, and caseId should be from a call to POST /organization/cases.

See SPL UI Protype (Figma)

Parameters

No parameters

Request body

application/JSON

• Example Value

Responses

IMPLEMENTED: POST /case/point

Creates a new point of concern to be associated with the case.

See SPL UI Protype (Figma)

Parameters

No parameters

Request body

application/JSON

• Example Value

Responses

Implemented: POST /case/consent-to-publishing

Captures user consent to having their data published in the aggregated anonymized JSON file that is available to public.

Parameters

No parameters

Request body

application/JSON

• Example Value

Responses

IMPLEMENTED: POST /case/stage

Updates the state of the case from unpublished to staging.

See SPL Data States (For MVP1)

Parameters

No parameters

Request body

application/JSON

• Example Value

Responses

IMPLEMENTED: POST /cases/publish

Moves the state of the cases from staging to published and generates JSON file containing aggregated anonymized points of concern data. JSON file is then pushed to the endpoint responsible for hosting the published data (this functionality is implemented by HA).

See SPL Data States (For MVP1)

Parameters

No parameters

Request body

application/JSON

• Example Value

Responses

IMPLEMENTED: PUT /case/point

Updates an existing point of concern

See SPL UI Protype (Figma)

Parameters

No parameters

Request body

application/JSON

• Example Value

Responses

IMPLEMENTED: DELETE /case/point

Deletes the point of concern having the ID corresponding with the pointID param.

See SPL UI Protype (Figma)

Parameters

No parameters

Request body

application/JSON

• Example Value

Responses