DELETE /api/tickets/{TicketID}/marks/{UserID}

Removes the user's mark from a ticket that the user has previously marked.

Authorization Roles/Permissions: Must be logged in. Must be an authorized user for the resource the ticket relates to, and must be the same user who created the mark that is being removed.

This topic includes the following sections:

HTTP Method


Back to top



Back to top

Sample Request

The example below shows a request to remove a mark from the specified ticket.

Request URL


Sample request headers

DELETE /api/discussions/ticket25687.acmepaymentscorp/marks/522320b9-cb6b-495d-ae07-e4b3bfdb3f6a.acmepaymentscorp HTTP/1.1
Host: {hostname}
Accept: */*
Content-Type: application/x-www-form-urlencoded; charset=UTF-8

Sample request body

Not applicable.

Back to top

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 format (*/*)
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
TicketID Path string Required The unique ID for a specific ticket.
UserID Path string Required The unique ID for a specific user.

Back to top


If successful, this operation returns HTTP status code 200, with a number indicating the total number of marks on the ticket after one mark was removed.

Back to top

Sample Response

The sample response below shows successful completion of this operation. The specified ticket now has 5 marks.

Sample response headers

HTTP/1.1 200 OK
Content-Type: text/plain
Date: Thu, 18 Jul 2013 20:21:58 GMT

Sample response body


Back to top

Response Headers

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

Header Description
Content-Type text/plain

Back to top

Response Body

Name Type Description
Response string The updated number of marks for the specified ticket.

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
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.

Back to top

Related Topics