.TH "GCLOUD_ALPHA_SERVICES_API\-KEYS_LOOKUP" 1



.SH "NAME"
.HP
gcloud alpha services api\-keys lookup \- look up resource name of a key string



.SH "SYNOPSIS"
.HP
\f5gcloud alpha services api\-keys lookup\fR \fIKEY_STRING\fR [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(ALPHA)\fR Look up resource name of a key string.



.SH "EXAMPLES"

Look up resource name of a key string named my\-key\-string:

.RS 2m
$ gcloud alpha services api\-keys lookup my\-key\-string
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m
\fIKEY_STRING\fR

Key string of the key


.RE
.sp

.SH "GCLOUD WIDE FLAGS"

These flags are available to all commands: \-\-access\-token\-file, \-\-account,
\-\-billing\-project, \-\-configuration, \-\-flags\-file, \-\-flatten,
\-\-format, \-\-help, \-\-impersonate\-service\-account, \-\-log\-http,
\-\-project, \-\-quiet, \-\-trace\-token, \-\-user\-output\-enabled,
\-\-verbosity.

Run \fB$ gcloud help\fR for details.



.SH "NOTES"

This command is currently in alpha and might change without notice. If this
command fails with API permission errors despite specifying the correct project,
you might be trying to access an API with an invitation\-only early access
allowlist. These variants are also available:

.RS 2m
$ gcloud services api\-keys lookup
.RE

.RS 2m
$ gcloud beta services api\-keys lookup
.RE