feat(api): make Client support optional API key and custom base URL#7
Merged
Conversation
Allow the Client class to be initialized with flexible authentication and base URL configurations: 1. API key only: Uses default production API base URL with authentication 2. Base URL only: Uses custom base URL without authentication (for local servers) 3. Both: Uses custom base URL with authentication This enables the client to work with: - Production API (requires API key) - Local HTTP servers (no authentication required) - Custom API backends (with or without authentication) The api_key parameter is now optional, and a new base_url parameter has been added. Headers are conditionally set based on whether an API key is provided. Existing code using Client(api_key="...") remains fully compatible.
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 the Client class to be initialized with flexible authentication and base URL configurations:
This enables the client to work with:
The api_key parameter is now optional, and a new base_url parameter has been added. Headers are conditionally set based on whether an API key is provided. Existing code using Client(api_key="...") remains fully compatible.