PUT /api/businesses/{BusinessID}/ticketsettings

Updates the configurable ticket 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: Site Admin.

This topic includes the following sections:

HTTP Method

PUT

URL

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

Sample Request

The example below shows a request to specify custom workflow for tickets and ticket comments.

Sample Request URL

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

Sample request headers

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

Sample request body

{
  "TicketSupport" : "com.soa.feature.enabled",
  "TicketWorkflowDefKey" : "workflow:definition:ticket",
  "TicketCommentWorkflowDefKey" : "workflow:definition:comment",
  "Visibility" : "com.soa.visibility.apivisibility"
  "MarkdownSupport" : "com.soa.feature.enabled"
  "ExternalLinkSupport" : "com.soa.feature.disabled"
  }

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
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.
ticketSettings	Body	TicketSettings	Required	Contains information about a business's settings in relation to tickets.

Response

If successful, this operation returns HTTP status code 200, with the updated ticket 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: Tue, 12 May 2015 12:17:50 GMT

Sample response body: application/json

{
  "TicketSupport" : "com.soa.feature.enabled",
  "TicketWorkflowDefKey" : "workflow:definition:ticket",
  "TicketCommentWorkflowDefKey" : "workflow:definition:comment",
  "Visibility" : "com.soa.visibility.apivisibility"
  "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
TicketSettings	TicketSettings	Contains information about a business's settings in relation to tickets.

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.
500	An error occurred processing the call.

More information about Akana API Platform API error messages.

Related Topics