azure-openai
For azure-openai
, we provide a client that can be used to interact with the OpenAI API hosted on Azure using the /chat/completions
endpoint.
Example:
api_version
is required. Azure will return not found if the version is not specified.
The options are passed through directly to the API, barring a few. Here’s a shorthand of the options:
BAML-specific request options
These unique parameters (aka options
) modify the API request sent to the provider.
You can use this to modify the azure api key, base url, and api version for example.
Will be injected via the header API-KEY
. Default: env.AZURE_OPENAI_API_KEY
API-KEY: $api_key
The base URL for the API. Default: https://${resource_name}.openai.azure.com/openai/deployments/${deployment_id}
May be used instead of resource_name
and deployment_id
.
See the base_url
field.
See the base_url
field.
Will be passed via a query parameter api-version
.
Additional headers to send with the request.
Example:
The role to use if the role is not in the allowed_roles. Default: "user"
usually, but some models like OpenAI’s gpt-4o
will use "system"
Picked the first role in allowed_roles
if not “user”, otherwise “user”.
Which roles should we forward to the API? Default: ["system", "user", "assistant"]
usually, but some models like OpenAI’s o1-mini
will use ["user", "assistant"]
When building prompts, any role not in this list will be set to the default_role
.
Which role metadata should we forward to the API? Default: []
For example you can set this to ["foo", "bar"]
to forward the cache policy to the API.
If you do not set allowed_role_metadata
, we will not forward any role metadata to the API even if it is set in the prompt.
Then in your prompt you can use something like:
You can use the playground to see the raw curl request to see what is being sent to the API.
Whether the internal LLM client should use the streaming API. Default: true
Then in your prompt you can use something like:
Which finish reasons are allowed? Default: null
Will raise a BamlClientFinishReasonError
if the finish reason is not in the allow list. See Exceptions for more details.
Note, only one of finish_reason_allow_list
or finish_reason_deny_list
can be set.
For example you can set this to ["stop"]
to only allow the stop finish reason, all other finish reasons (e.g. length
) will treated as failures that PREVENT fallbacks and retries (similar to parsing errors).
Then in your code you can use something like:
Which finish reasons are denied? Default: null
Will raise a BamlClientFinishReasonError
if the finish reason is in the deny list. See Exceptions for more details.
Note, only one of finish_reason_allow_list
or finish_reason_deny_list
can be set.
For example you can set this to ["length"]
to stop the function from continuing if the finish reason is length
. (e.g. LLM was cut off because it was too long).
Then in your code you can use something like:
Provider request parameters
These are other options
that are passed through to the provider, without modification by BAML. For example if the request has a temperature
field, you can define it in the client here so every call has that set.
Consult the specific provider’s documentation for more information.
BAML will auto construct this field for you from the prompt
BAML will auto construct this field for you based on how you call the client in your code
For all other options, see the official Azure API documentation.