Delete a notice from manitu
Removes a notice of this access from the customer panel.
Removes a notice manitu left for the calling access in the customer panel, by its notice_id. The notice cannot be restored. Marking it read instead is manitu_access_notice_setPOST /v1/access/notice/set. Made with a session of the customer panel, the call is carried out at once; otherwise the caller confirms it first: approval_required with the way call_again, then the same call again with its approval_token - unless the access is set to make such changes without asking.
Counts against: writes (60 per hour per account)
manitu_access_notice_delete on https://mcp.manitu.de/mcpAnnotations as tools/list sends them
Description for the model
Removes a notice manitu left for the access this connection uses from the manitu customer panel, by its notice_id - the user cannot get it back. Only when the user asks for it; to stop it showing as new, manitu_access_notice_setPOST /v1/access/notice/set (read) is enough.
Arguments
notice_id (required)integer | stringThe notice_id of the notice. Never guess one.
approval_tokenstringwrite-onlyThe token of the way call_again from the approval_required answer of the same call - only after the user said yes to everything in its elements. Valid 15 minutes, once.
Result structuredContent, checked against the schema
notice_idintegerAuthentication
One of X-API-Key, Authorization: Bearer … - never more than one in a request. More
Request body JSON; unknown fields are refused
notice_id (required)integer | stringThe notice_id of the notice.
approval_tokenstringwrite-onlyThe token of the way call_again from the approval_required answer of the same call - only after the user said yes to everything in its elements. Valid 15 minutes, once.
Response in data; the rest of the body as on every call
notice_idintegerStatuses
200Success.400The input is wrong, or the request itself (INVALID_INPUT). Each entry names its field and its reason - correct the input and call again.401No credential was presented, or it was not recognised (UNAUTHENTICATED).403The credential is valid, but may not do this (PERMISSION_DENIED). The reason says why - another credential is the way, not a repeat.429Too many calls. The Retry-After header says when to try again.500The server failed. Nothing about the request was wrong. Whether a change took effect is not known - check before trying it again.503The channel this operation forwards through is unavailable.