The workflow to authentify is based on Oauth2 protocal. To have access to Domoscio functionalities the user should follow these steps:

• AuthorizationToken:
  

  The AuthorizationToken is given to the user when he starts working with the Domoscio API. This token must remain secret and used only once.

  1. The AuthorizationToken should be used inside the Header of the request when calling the API for the first time:
     Authorization: Bearer < AuthorizationToken >
  2. Inside the response Header, the AccessToken and RefreshToken will be given:
     AccessToken: < AccessToken >
     RefreshToken: < RefreshToken >
     

• AccessToken and RefreshToken:
  

  1. The user can now access API resources and functionalities with the AcessToken. Like the AuthorizationToken, the AccessToken should be used inside the Header of the request:
     AccessToken: < AccesToken >
     
  2. This AccessToken expires after two hours and an error message will be returned when calling the API:
     401 Error: {message: 'Expired Token. No Refresh Token provided'}
     
  3. The RefreshToken should now be used in the header of the API request with the expired AccessToken:
     AccessToken: < ExpiredAccessToken >
     RefreshToken: < RefreshToken >
     
  4. Get the new AccessToken in the Header of the API response:
     AccessToken: < NewAccessToken >
     
  5. The new AccessToken can be used as usual until it expires.

A KnowledgeGraph (KG) is the first object to instantiate while setting up your content on our API. It is the top level of aggregation for knowledge nodes and edges. You can use it to describe your course, a book or even your whole knowledge map.

A KnowledgeNode (KN) is the second object to instantiate while setting up your content on our API. It is the central model of the application; it can be linked to multiple KnowledgeGraphs. You can use it to describe your content architecture, i.e skills, knowledges, know-hows, etc.