API planning

General comments

In the long run DiMe should perhaps follow Principles of good RESTful API Design, for example using PUT and PATCH for updating existing objects instead of POST'ing with the id given. But for now we'll stick with the old way in order to be consistent with the rest of the DiMe API.

Also API versioning should be introduced at some point, e.g. /api/v1, /api/v2 and so on.

Profile API

POST api/profile (adding new profile, profile name response: profile ID)
POST api/profile (modifying a profile if the ID is given in the posted data)
GET api/profile/{ID} (get the content of profile, what is in the profile?)
DELETE api/profile/{ID} (deleting obviously)

Example

POST api/profile with the data:

{
  name: “Kai’s formula profile”,
  search_keywords: [“x”, “y”, ],
  tags: [{ id: tag_id_x}, {id: tag_id_y}],	
}

DiMe response:

{
  id: 83724, 
  name: “Kai’s formula profile”,
  search_keywords: [“x”, “y”, ],
  tags: [{ id: tag_id_x}, {id: tag_id_y}],	
}

Model API

register model (register name, get ID?)

Tag API

Update

Account API

Create, remove, forget, account pw

Status API

DiMe event count DiMe document count DiMe status, active loggers, API activity (log)