POST /api/tickets/{TicketID}/actions
Executes an action on the specified ticket.
Authorization Roles/Permissions: Must be logged in. Must be an admin for the resource the ticket relates to.
This topic includes the following sections:
HTTP Method
POST
URL
https://{hostname}/api/tickets/{TicketID}/actions
Sample Request
The example below shows a request message resolving a ticket.
Sample Request URL
https://{hostname}/api/tickets/ticket25687.acmepaymentscorp/actions
Sample request headers
POST /api/tickets/ticket25687.acmepaymentscorp/actions HTTP/1.1 Host: {hostname} Accept: */* Content-Type: application/json; charset=UTF-8 X-Csrf-Token_acmepaymentscorp: TokenID%3D8ed70a13-8469-11e8-b37a-b155e4eabeb8%2CexpirationTime%3D153...
Sample request body
{ "ActionName":"ticket.action.resolve", "Comments":"Bug is fixed. Resolving this ticket." }
Request Headers
For general information on request header values, refer to HTTP Request Headers.
Header | Description |
---|---|
Accept | Any Accept header value that supports a response Content-Type of text/plain is valid; for example, */*. |
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 |
---|---|---|---|---|
TicketID | Path | string | Required | The unique ID for a specific ticket. |
Action | Body | Action | Required |
Contains information about an action performed on a resource as part of a workflow-related activity. For information on possible values for workflow actions relating to Tickets, see Tickets: Valid Workflow Actions. ActionName is required. |
Response
If successful, this operation returns HTTP status code 200, with the updated ticket state value in the response.
Sample Response
The sample response below shows successful completion of this operation.
Sample response headers
HTTP/1.1 200 OK Content-Type: text/plain Date: Tue, 16 Jul 2013 20:42:52 GMT
Sample response body
RESOLVED
Response Headers
For general information on response header values, refer to HTTP Response Headers.
Header | Description |
---|---|
Content-Type | text/plain |
Response Body
Name | Type | Description |
---|---|---|
Response | string | The updated value for the ticket's state. |
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 |
---|---|
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.