PUT /api/businesses/{BusinessID}/usersettings

Updates the configurable user settings for a business on the platform.

Note: When you change a setting, it might take up to five minutes for the change to take effect.

Authorization Roles/Permissions: Must be logged in. Must have Modify permission for the resource. Site Admin or other authorized Admin.

This topic includes the following sections:

HTTP Method

PUT

Back to top

URL

https://{hostname}/api/businesses/{BusinessID}/usersettings

Back to top

Sample Request

The example below shows a request to update the user settings for the specified business.

Request URL

https://{hostname}/api/businesses/tenantbusiness.acmepaymentscorp/usersettings

Sample request headers

Content-Type: application/json
Accept: application/json
X-Csrf-Token_acmepaymentscorp":"TokenID%3D8ed70a13-8469-11e8-b37a-b155e4eabeb8%2CexpirationTime%3D153...

Sample request body

{
  "NewsUpdateNotification" : "com.soa.feature.enabled",
  "EnforceChallengesSetupOnLogin" : "com.soa.feature.enabled",
  "SelfSignup" : "com.soa.feature.enabled",
  "InviteUnregisteredUsers" : "com.soa.feature.enabled",
  "ResetValidCodeHours" : 24,
  "SignupUserValidDays" : 7,
  "AddedUserValidDays" : 30,
  "InvitedUserValidDays" : 7
}

Back to top

Request Headers

For general information on request header values, refer to HTTP Request Headers.

Header Description
Accept

application/json, application/xml

application/vnd.soa.v71+json, application/vnd.soa.v71+xml

application/vnd.soa.v72+json, application/vnd.soa.v72+xml

application/vnd.soa.v80+json, application/vnd.soa.v80+xml

application/vnd.soa.v81+json, application/vnd.soa.v81+xml

Content-Type

Any one of the following media types is valid for the request Content-Type:

application/json or application/xml

application/vnd.soa.v71+json or application/vnd.soa.v71+xml

application/vnd.soa.v72+json or application/vnd.soa.v72+xml

application/vnd.soa.v80+json or application/vnd.soa.v80+xml

application/vnd.soa.v81+json or application/vnd.soa.v81+xml

X-Csrf-Token_{fedmemberID} The CSRF prevention header; may or may not be required, depending on platform settings. See CSRF Prevention on the Platform. By default, the CSRF header is not required for GET operations and is required for all others, with a few exceptions relating to user login.

Back to top

Request Parameters

Parameter Parm Type Data Type Required Description
BusinessID Path string Required The unique ID for a specific business organization on the platform.
BusinessUserSettings Body BusinessUserSettings Required Default settings to apply to all users within the business.

Back to top

Response

If successful, this operation returns HTTP status code 200, with the updated settings.

Back to top

Sample Response

The sample response below shows successful completion of this operation.

Sample response headers: application/json

Status Code: 200 OK
Content-Type: application/json
Expires: Mon, 05 Jan 2015 15:26:35 GMT

Sample response body: application/json

{
  "NewsUpdateNotification" : "com.soa.feature.enabled",
  "EnforceChallengesSetupOnLogin" : "com.soa.feature.enabled",
  "SelfSignup" : "com.soa.feature.enabled",
  "InviteUnregisteredUsers" : "com.soa.feature.enabled",
  "ResetValidCodeHours" : 24,
  "SignupUserValidDays" : 7,
  "AddedUserValidDays" : 30,
  "InvitedUserValidDays" : 7
}

Back to top

Sample response headers: application/vnd.soa.v72+xml

Status Code: 200 OK
Content-Type: application/vnd.soa.v72+xml
Expires: Mon, 05 Jan 2015 15:27:36 GMT

Sample response body: application/vnd.soa.v72+xml

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<BusinessUserSettings xmlns="http://soa.com/xsd/business/1.0" xmlns:ns2="http://soa.com/xsd/legals/1.0" 
xmlns:ns3="http://soa.com/xsd/dnmodel/1.0" xmlns:ns4="http://soa.com/xsd/api/1.0">
  <NewsUpdateNotification>com.soa.feature.enabled</NewsUpdateNotification>
  <EnforceChallengesSetupOnLogin>com.soa.feature.enabled</EnforceChallengesSetupOnLogin>
  <SelfSignup>com.soa.feature.enabled</SelfSignup>
  <InviteUnregisteredUsers>com.soa.feature.enabled</InviteUnregisteredUsers>
  <ResetValidCodeHours>24</ResetValidCodeHours>
  <SignupUserValidDays>7</SignupUserValidDays>
  <AddedUserValidDays>30</AddedUserValidDays>
  <InvitedUserValidDays>7</InvitedUserValidDays>
</BusinessUserSettings>

Back to top

Response Headers

For general information on response header values, refer to HTTP Response Headers.

Header Description
Content-Type

application/json, application/xml

application/vnd.soa.v71+json, application/vnd.soa.v71+xml

application/vnd.soa.v72+json, application/vnd.soa.v72+xml

application/vnd.soa.v80+json, application/vnd.soa.v80+xml

application/vnd.soa.v81+json, application/vnd.soa.v81+xml

Back to top

Response Body

Name Type Description
BusinessUserSettings BusinessUserSettings Default settings to apply to all users within the business.

Back to top

Error Codes/Messages

If the call is unsuccessful an error code/message is returned. One or more examples of possible errors for this operation are shown below.

Item Value
400 Bad request: Returned if the client sends invalid parameters or body content. For example, you might get this response if you send an incorrect JSON object in the request, or specified the wrong media type in the Content-Type header.
401 Unauthorized. For example, you would get this response if you didn't include the custom X-Csrf-Token_{fedmemberID} header in the request, when it was required by the platform settings; or if you included an invalid or expired value for this header. You would also get this response for any operation that requires login (almost all) if the login cookie was missing.
405

Method Not Allowed. For example, you might get this if you specified an invalid Accept header or omitted a required Content-Type header, or used the wrong HTTP verb.

You would also get it if you used the wrong HTTP verb.

500 An error occurred processing the call.

More information about Akana API Platform API error messages.

Back to top

Related Topics