REST - Person - AccountSetting

REST-Interface

Get account-settings

This returns all stored account-settings from db, but normally clients should use "LoginData.accountSettings".
URL
GET <application-url>/api/person/accountsetting

Produces

application/json
application/xml

List<com.matterial.mtr.api.object.AccountSetting>

  • 200 OK
  • 500 INTERNAL_SERVER_ERROR

Permission
Login

Sample
GET http://localhost:8080/mtr-backend/api/person/accountsetting


Update account-setting

Updates a single account-setting by "key", but normally clients should use "Update account-settings" just storing "loginData.accountSettings".
URL
PUT <application-url>/api/person/accountsetting

Consumes

application/json
application/xml

com.matterial.mtr.api.object.AccountSetting

Produces

application/json
application/xml

com.matterial.mtr.api.object.AccountSetting

  • 200 OK
  • 400 BAD_REQUEST
  • 304 NOT_MODIFIED
  • 500 INTERNAL_SERVER_ERROR

Permission
Login

Sample
PUT http://localhost:8080/mtr-backend/api/person/accountsetting


Update account-settings

Clients can simply store "loginData.accountSettings".
URL
PUT <application-url>/api/person/accountsetting/all

Consumes

application/json
application/xml

Map<String, String>
json
{
"accountSetting.language.ui": "de",
"accountSetting.language.content": "de",
"accountSetting.client": 3,
"accountSetting.showHelp": true,
"accountSetting.newsSubscriber": "de",
"accountSetting.showArchiveOnLogin": false,
"accountSetting.disableRightsOnLogin": false,
"accountSetting.showWelcomePageOnLogin": true,
}

  • 200 OK
  • 500 INTERNAL_SERVER_ERROR

Permission
Login

Sample
PUT http://localhost:8080/mtr-backend/api/person/accountsetting/all

×
Peter's Problem.