Closed StephenOTT closed 7 years ago
Proposed Endpoints for v1
GET cases
GET cases/:caseid
GET cases/:caseid/records
GET cases/:caseid/records/:recordid
GET cases/:caseid/records/:recordid/attachments
GET cases/:caseid/statuses
GET cases/:caseid/statuses/:statusid
GET assets
GET assets/:assetid
GET services
GET services/:serviceid
GET services/:serviceid/status
POST services/:serviceid/activation
POST services/:serviceid/submission
GET dashboards
GET dashboards/:dashboardid
GET dashboards/:dashboardid/widgets
GET dashboards/:dashboardid/widgets/:widgetid
GET personas
GET personas/:personaid
PATCH personas/:personaid
PUT personas/:personaid
GET messages
GET messages/:messageid
POST messages/:messageid/acknowledgement
GET topics
GET topics/:topicid
GET topics/:topicid/subscriptions
POST topics/:topicid/subscriptions
PATCH topics/:topicid/subscriptions/:subscriptionid
PUT topics/:topicid/subscriptions/:subscriptionid
POST services/:serviceid/activation
Explanation:
formio.dev/
The Type is the system to where the data is being routed to.
Should likely also store the Service ID that was used when the Activation was created.
POST services/:serviceid/submission
Explanation:
Addtional Endpoints to be considered:
@mario-digitalstate
Need to add additional Endpoints for "Communications" / Common Alerts.
GET individuals
GET individuals/:individualid
GET individuals/:individualid/personas
GET individuals/:individualid/personas/:personasid
Notes: Activation: Id Activation Key Service id Userid Anonymousid Exipiration datetime Save for later object Json
Introduction of highly refined and opinionated Portal API for use by Front-End applications that are used by Individuals/Organizations. (Non-Admin/non-gov users). These endpoints are in addition to the current API.