跳到主要内容

terminateRemove

terminateRemove(TerminateRequestDto)

PUT /api/2.0/people/remove/terminate

Terminate the data deletion

Cancels the data deletion queued for the user with the ID specified in the request. The caller needs the permission to edit users. The operation is idempotent and returns no body: it drops the job from the queue, and doing so when nothing is queued, or when the job has already finished, changes nothing and still answers 200. Cancelling does not restore the data the job has already erased, and a cancelled job cannot be resumed - start a new one through POST api/2.0/people/remove/start. To find out whether the job is still running, read GET api/2.0/people/remove/progress/{userId} before and after this call.

Parameters​

NameInTypeDescriptionNotes
TerminateRequestDtobodyTerminateRequestDto[optional]

Responses​

Status codeDescriptionTypeResponse headers
200The queued deletion is cancelled, or there was nothing to cancel. No content is returned-X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset
400The request body cannot be read or has no userId--
403No permissions to perform this action--
401UnauthorizedErrorApiResponse-
429Too Many Requests.ErrorApiResponseRetry-After
500Internal Server Error.ErrorApiResponse-
502Bad Gateway. Returned by the reverse proxy, response body may be HTML and not JSON.--
503Service Unavailable. Returned by the reverse proxy, response body may be HTML and not JSON.--

Return type​

null (empty response body)

Authorization​

Basic, OAuth2 (scopes: read, write), ApiKeyBearer, asc_auth_key, Bearer, OpenId

HTTP request headers​

  • Content-Type: application/json
  • Accept: application/json