Dismiss a suggestion series
POST/api/v1/suggestions/:id_suggestion/series/dismiss
Dismiss every occurrence of a recurring event, and keep future occurrences dismissed as they arrive.
This is the "stop suggesting my daily standup" operation. Dismissing one occurrence at a time would not stop tomorrow's from appearing; this records the disposition against the series itself.
POST /api/v1/suggestions/23/series/dismiss names suggestion 23. The
series acted on is whichever one that suggestion belongs to.
This surprises people, and it is deliberate: a client holding one occurrence rarely knows the series identifier, and this way it does not need to.
If the suggestion belongs to no series, the action affects that one
suggestion. The series_id in the response is null in that case, which
is how you can tell the two outcomes apart.
Your own suggestions, or those of a user you hold a timekeeping ability
over. Over a Bearer token this needs the jx:suggestions:write scope.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 500
- 503
The series was dismissed.
A 400 Bad Request is returned when the client request was malformed,
invalid, or otherwise could not be processed as-is. Usually, the cause for
the error is included in the error.message field of the response, and the
client should correct the request and try again.
See also Core Concepts#Error Responses.
Not authenticated - you must be signed in to access this resource. Please check the section of the documentation on authentication.
A 403 Forbidden response means that you are not authorized to perform
this action or access this object, or the object does not exist at all.
The client request may have been valid but the client does not have permission to access the requested resource or perform the requested action.
In most cases, the system will not return a 404 Not Found error response;
it returns 403 Forbidden both when the object doesn't exist at all,
and also when it exists but the client does not have permission to access it.
This is a security measure to prevent unauthorized users from determining
whether an object exists or not.
See also Core Concepts#Error Responses.
Not found - the requested resource could not be found or does not exist. This may also include cases where the resource does exist, but the client does not have permission to access that resource.
In most cases, the system will not return a 404 Not Found error response;
it returns 403 Forbidden both when the object doesn't exist at all,
and also when it exists but the client does not have permission to access it.
This is a security measure to prevent unauthorized users from determining
whether an object exists or not.
See also Core Concepts#Error Responses.
Internal server error; an unexpected error occurred on the server. This could be due to a temporary condition or might be the result of a bug in the server software. Also, in some cases, an incorrect client input can trigger this error, and can be resolved by correcting the input.
If the error persists, please contact support along along with the following details when possible:
- any error messages received from the server
- the full request and response details (full headers and body)
- a description of the steps that led to the error
- the time range when it occurred.
Service unavailable - the server is currently unable to handle the request, usually due to maintenance activity on the server. Check if the server's web interface is currently available, or try again later.