-
Notifications
You must be signed in to change notification settings - Fork 0
Backend API Docs
Martin Leopold edited this page Oct 13, 2016
·
8 revisions
- General
- Authentication
-
Admin
POST /admin/userPATCH /admin/userDELETE /admin/userGET /admin/user_listGET /admin/user_stats
-
User Sessions
GET /session/userdataGET /session/resetGET /session/refreshPOST /session/imagesGET /session/imagesDELETE /session/imagesPOST /session/coverGET /session/coverGET /session/archive
- All (non-
GET) requests need to be sent with a header ofContent-Type: application/json - All requests except
POST /loginneed to be authenticated by providing a valid token. - The token for the next request is obtained in the
tokenfield of each successful response. - The token is can be provided by any of the following methods:
- A
X-Access-Tokenheader (preferred) - A
tokenquery parameter - A
tokenbody parameter (for requests withContent-Type: application/json)
- A
- Status Code:
200 -
statusHolds the string'success' -
messageDescriptive message -
tokenAccess token for next request
- Status Codes:
4xxor5xx -
statusHolds the string'error' -
messageError message
- Parameters (Body)
emailpassword
- Response (200)
-
dataidnameemailbrandstheme_color
-
- Parameters
- none
- Response (200)
- empty
POST /admin/user
PATCH /admin/user
DELETE /admin/user
GET /admin/user_list
GET /admin/user_stats
GET /session/userdata
GET /session/reset
GET /session/refresh
POST /session/images
GET /session/images
DELETE /session/images
POST /session/cover
GET /session/cover
GET /session/archive