Deletes a ServiceAccountKey. Deleting a service account key does not revoke short-lived credentials that have been issued based on the service account key.
When possible, avoid using the - wildcard character, because it can cause response messages to contain misleading error codes. For example, if you try to access the service account key projects/-/serviceAccounts/fake@example.com/keys/fake-key, which does not exist, the response contains an HTTP 403 Forbidden error instead of a 404 Not Found error.
Authorization requires the following IAM permission on the specified resource name:
iam.serviceAccountKeys.delete
Request body
The request body must be empty.
Response body
If successful, the response body is an empty JSON object.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-01-16 UTC."],[[["This endpoint deletes a specified ServiceAccountKey, but does not revoke any short-lived credentials previously issued with that key."],["The HTTP request uses a `DELETE` method with a URL that follows gRPC Transcoding syntax, requiring the full resource name of the key to be deleted."],["The `name` parameter is mandatory and specifies the resource name of the ServiceAccountKey to delete, following a specific format that includes the project ID, service account identifier, and key ID."],["The request body must be empty for this operation to be performed."],["Successful deletion of a ServiceAccountKey results in an empty JSON object response."]]],[]]
