Feat: Adding Ability to add API key per Request / Endpoint #453
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.
Overview
Internal ticket AE-1090, resolution to add feature for client level / request level API key.
Follow up:
Will need to update these docs
https://docs.runpod.io/sdks/python/endpoints
GraphQL Calls
GraphQL calls I don't believe have a client / are stateless:
So the way those can work is such that we do:
Endpoint:
These have an internal state, so we can instantiate the Endpoint with the api key:
Before:
Now supported: