As an alternative, you can use the - wildcard character instead of the project ID:
projects/-/serviceAccounts/{EMAIL_ADDRESS}
projects/-/serviceAccounts/{UNIQUE_ID}
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 projects/-/serviceAccounts/fake@example.com, 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.create
Request body
The request body contains data with the following structure:
[[["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-05-21 UTC."],[[["This page details how to create a ServiceAccountKey via an HTTP POST request to a specific URL structure that follows gRPC Transcoding syntax."],["The request requires a `name` parameter in the URL, which must follow a specific format indicating the service account's resource name, including the project ID and email or unique ID, with specific authorization."],["The request body should include the desired `privateKeyType` and `keyAlgorithm` for the ServiceAccountKey, with defaults available if not specified."],["A successful request will return a newly created instance of the ServiceAccountKey in the response body."],["Authorization for this process requires one of two specified OAuth scopes: either `https://www.googleapis.com/auth/iam` or `https://www.googleapis.com/auth/cloud-platform`."]]],[]]
