feat: add custom session/client injection for proxy authentication#159
Merged
feat: add custom session/client injection for proxy authentication#159
Conversation
Allow users to pass a pre-configured requests.Session or httpx.AsyncClient to TavilyClient, AsyncTavilyClient, and TavilyHybridClient. This enables enterprise environments that proxy Tavily traffic through API gateways to use their own auth headers without needing a Tavily API key. When a custom session/client is provided, api_key becomes optional, external sessions are not closed by the SDK, and custom headers/proxies take precedence over defaults.
Contributor
Author
|
Fixes TAV-5269 |
pulvedu
approved these changes
Mar 9, 2026
This was referenced Mar 9, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Allow users to pass a pre-configured requests.Session or httpx.AsyncClient
to TavilyClient, AsyncTavilyClient, and TavilyHybridClient. This enables
enterprise environments that proxy Tavily traffic through API gateways to
use their own auth headers without needing a Tavily API key. When a custom
session/client is provided, api_key becomes optional, external sessions are
not closed by the SDK, and custom headers/proxies take precedence over defaults.