Custom Query Parameters on URL for API Calls #215
Merged
Conversation
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
2 participants
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 addresses issue: #212
This implements custom parameters for Live/Prerecorded/Manage Clients.
This implements:
Classas well as any arbitrate values (**kwargs) which will be passed into callback functions.**kwargs) which will be passed any class that extends the ManageClient. This allows for custom params not related to Deepgram APIs.examples/streaming/microphoneto show how you can use these new capabilities in an application.Verified that all examples work:
examples/manageexamples/streamingexamples/prerecordedUse this PR as the basis of updating https://github.com/deepgram/streaming-test-suite. You can find that implementation in this PR deepgram/live-streaming-starter-kit#11