Using Custom Add On Parameters with SDKs
Learn how to use custom add on parameters to set arbitrary key/value pairs with the Deepgram SDKs.
Learn how to use custom add on parameters to set arbitrary key/value pairs with the Deepgram SDKs.
The Deepgram JS SDK has defined typed parameters, but also allows for arbitrary key/value pairs. You can provide custom parameters when using the JS SDK to make an API Request even if the parameter isn’t defined as a type.
This is useful if you want to use a feature of the Deepgram API that isn’t officially supported in the JS SDK.
The Deepgram Python SDK has defined option parameters, but also allows for arbitrary key/value pairs. You can provide custom parameters when using the Python SDK to make an API Request even if the parameter isn’t defined as an option.
This is useful if you want to use a feature of the Deepgram API that isn’t officially supported in the Python SDK.
The Deepgram .NET SDK has defined option parameters, but also allows for arbitrary key/value pairs. You can provide custom parameters when using the .NET SDK to make an API Request even if the parameter isn’t defined as an option.
This is useful if you want to use a feature of the Deepgram API that isn’t officially supported in the .NET SDK.
The Deepgram Go SDK has defined option parameters, but also allows for arbitrary key/value pairs. You can provide custom parameters when using the Go SDK to make an API Request even if the parameter isn’t defined as an option.
This is useful if you want to use a feature of the Deepgram API that isn’t officially supported in the Go SDK.
The Deepgram Java SDK uses a typed builder pattern for all request parameters. For parameters not yet supported in the SDK, you can pass them as additional query parameters via RequestOptions.
flux-general-multi uses the language_hint query parameter on the /v2/listen WebSocket endpoint.