Skip to content

Conversation

@shsteimer
Copy link

Please ensure your pull request adheres to the following guidelines:

  • make sure to link the related issues in this description
  • when merging / squashing, make sure the fixed issue references are visible in the commits, for easy compilation of release notes

Related Issues

Thanks for contributing!

@shsteimer shsteimer requested review from dzehnder and solaris007 July 16, 2025 16:45
config.clientSecret,
config.redirectUri,
);
this.apiKey = config.apiKey;
Copy link
Author

@shsteimer shsteimer Jul 16, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This may warrant a discussion if this is appropriate way to auth with these APIs or not.

My understanding is that the oath client used for the GSC apis that exist in this module uses OAUTH on behalf of the customer. In this case, I don't think we want to do that.

Both of these APIs support API key auth, subject to some rate limits. Would require us to create and manage that Key, but that I assume should be simple enough. But happy to discuss and if using oauth is the preferred route, it should be a simple change.

https://developers.google.com/speed/docs/insights/v5/get-started#APIKey
https://developer.chrome.com/docs/crux/api#crux_api_key

@github-actions
Copy link

This PR will trigger a minor release when merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants