GET /api/businesses/{BusinessID}/discussionsettings
Returns information about the configurable discussion settings for a business on the platform.
Authorization Roles/Permissions: Site Admin.
This topic includes the following sections:
HTTP Method
GET
URL
https://{hostname}/api/businesses/{BusinessID}/discussionsettings
Sample Request
The example below shows a request to get the discussion settings for the specified business.
Sample Request URL
https://{hostname}/api/businesses/tenantbusiness.acmepaymentscorp/discussionsettings
Sample request headers
Content-Type: application/json X-Csrf-Token_acmepaymentscorp: TokenID%3D8ed70a13-8469-11e8-b37a-b155e4eabeb8%2CexpirationTime%3D153...
Sample request body
Not applicable.
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 |
Cookie | AtmoAuthToken_{fedmemberid}={cookie value, which usually starts with TokenID}—The platform cookie. This is the Akana API Platform authorization token, and must be sent with every API request that requires login. For more information and an example, see Session cookies. |
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. |
Request Parameters
Parameter | Parm Type | Data Type | Required | Description |
---|---|---|---|---|
BusinessID | Path | string | Required | The unique ID for a specific business organization on the platform. |
Response
If successful, this operation returns HTTP status code 200, with the discussion settings.
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: Thu, 14 May 2015 13:41:20 GMT
Sample response body: application/json
{ "DiscussionWorkflowDefKey" : "workflow:definition:discussion", "DiscussionCommentWorkflowDefKey" : "workflow:definition:comment" "AutoPublish" : false, "MarkdownSupport" : "com.soa.feature.enabled", "ExternalLinkSupport" : "com.soa.feature.disabled" }
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 |
Response Body
Name | Type | Description |
---|---|---|
BusinessDiscussionSettings | BusinessDiscussionSettings |
Contains information about default settings to apply to all discussions within the business. Note: If a custom workflow is specified the information about the workflow is returned. If no custom workflow is in use, the parameter is not included in the response. |
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 a malformed request; for example, invalid parameters or body content.For example, you might get this response if you specify an incorrect content type. |
500 | An error occurred processing the call. |
More information about Akana API Platform API error messages.