feat: add api_token parameter support for legacy compatibility #67
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.
This PR adds support for the legacy api_token parameter in both Replicate and AsyncReplicate client initialization as an alternative to bearer_token.
This enables backward compatibility with v1.x client code that uses:
Client(api_token="...")AsyncClient(api_token="...")The implementation:
Testing locally
gh pr checkout 66 # Replace with actual PR number scripts/test tests/test_api_token_compatibility.pyPrompts