POST
/v2/projects/{projectId}/start-batch-job/hard-delete-keysPermanently delete soft-deleted keys
Permanently deletes selected keys that have already been soft-deleted from a project. Supply keyIds with at least one identifier, and poll GET /v2/projects/{projectId}/batch-jobs/{id} to monitor progress.
- IdempotentThe SDK sends
Idempotency-Key, so a retried request is only applied once.
projectIdintegerrequired
The int64 identifier of the project containing the soft-deleted keys.
Permanent key deletion details. keyIds is required and must contain at least one identifier.
keyIdsarray<integer>required
Identifiers of the soft-deleted project keys to permanently delete. Must contain at least one identifier.
200Returns the batch job object with its identifier, type, status, progress, total item count, and creation and update times.
activityRevisionIdintegeroptional
The activity revision id, that stores the activity details of the job
authorobjectoptional
createdAtintegerrequired
The time when the job created
errorMessagestringoptional
If the job failed, this is the error message
idintegerrequired
Batch job id
progressintegerrequired
Total items, that have been processed so far
statusstringrequired
Status of the batch job
totalItemsintegerrequired
Total items
typestringrequired
Type of the batch job
updatedAtintegerrequired
The time when the job was last updated (status change)
400Returned when `keyIds` is missing or the request body fails validation.
codestringrequired
paramsarray<object>optional
401Returned when the request is not authenticated.
codestringrequired
paramsarray<object>optional
403Returned when the authenticated user does not have permission to run the batch job.
codestringrequired
paramsarray<object>optional
404Returned when the project or a referenced resource cannot be found.
codestringrequired
paramsarray<object>optional
Error handling
A 400 is returned when the request body is missing required fields or fails validation; a 401 is returned when the request is unauthenticated, a 403 when the authenticated user lacks access, and a 404 when the project or a referenced resource cannot be found. The projectId path parameter must identify the project to update. keyIds must contain at least one identifier, and the selected keys must be soft-deleted before permanent deletion.