docs: add sample code for authenticating with api keys #11023
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
blakeli0
reviewed
Jul 25, 2024
| We are actively exploring ways to improve the API Key experience. | ||
| Currently, to use an API Key with a Java client library, you need to set the header for the relevant service Client manually. | ||
| For example, to set the API Key with the [Language service](https://cloud.google.com/java/docs/reference/google-cloud-language/latest/overview): |
Contributor
There was a problem hiding this comment.
Do Language support API Keys?
Co-authored-by: Blake Li <blakeli@google.com>
blakeli0
approved these changes
Jul 26, 2024
lqiu96
pushed a commit
that referenced
this pull request
Jul 7, 2025
* docs: add sample code for authenticating with api keys * Update README.md Co-authored-by: Blake Li <blakeli@google.com> --------- Co-authored-by: Blake Li <blakeli@google.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #10921
This adds the current workaround for manually setting the API Key in the header when instantiating a client.