Skip to content

Latest commit

 

History

History
77 lines (63 loc) · 2.33 KB

userflow.md

File metadata and controls

77 lines (63 loc) · 2.33 KB

Standard userflow

Action Frontend API call
1. User signup /signup POST auth/users/
2. Confirm email link openchaver.com/activate/[uid]/[token] POST auth/users/activation/
2a. Request another email link /login on:login of inactive account POST auth/users/resend_activation/
2b. Request password reset link /reset-password POST auth/users/reset_password/
2c. Reset password openchaver.com/reset-password/[uid]/[token] POST auth/users/reset_password_confirm/
3. Login /login POST auth/token/login/
3a. Logout <Header /> Button click POST auth/token/logout/
4. Add a device to account POST devices/
5. Assign device to chaver POST chavers/

Note: From 3a and on a Authorization: 'Token {token}' header is required on the request.

2a. User requests another confirmation email POST auth/users/resend_activation/

{
	"email": "[email protected]"
}
  1. User adds a device * POST /devices/
{
	"name": "string"
}
  1. Assign device to a chaver (possibly with groups) * POST /chavers/
{
	"name": "string",
	"email": "[email protected]"
}

// change email or password

client -> turn on; asks for device id

Add a device Send {...Name_of_device} returns with device info with an {uid}

Add chavers

{
	"name": "string",
	"email": "[email protected]",
	"device": "uuid"
}

// delete/remove chaver

DELETE /chavers/{id}/

Setup a device POST http://localhost:61195/configure

{
	"device_id": "string"
}

Unregister device POST