POST /chat/completions

Servers

Request headers

Name Type Required Description
Content-Type String Yes The media type of the request body.

Default value: "application/json"

Request body fields

Name Type Required Description
stop Object No

Not supported with latest reasoning models o3 and o4-mini.

Up to 4 sequences where the API will stop generating further tokens. The returned text will not contain the stop sequence.

temperature Number No

What sampling temperature to use, between 0 and 2. Higher values like 0.8 will make the output more random, while lower values like 0.2 will make it more focused and deterministic. We generally recommend altering this or top_p but not both.

Default value: 1

audio Object No

Parameters for audio output. Required when audio output is requested with modalities: ["audio"]. Learn more.

audio.format String Yes

Specifies the output audio format. Must be one of wav, mp3, flac, opus, or pcm16.

Possible values:

  • "opus"
  • "mp3"
  • "flac"
  • "aac"
  • "pcm16"
  • "wav"
audio.voice Yes
tools[] Array No

A list of tools the model may call. Currently, only functions are supported as a tool. Use this to provide a list of functions the model may generate JSON inputs for. A max of 128 functions are supported.

tools[].function Object Yes
tools[].function.name String Yes

The name of the function to be called. Must be a-z, A-Z, 0-9, or contain underscores and dashes, with a maximum length of 64.

tools[].function.description String No

A description of what the function does, used by the model to choose when and how to call the function.

tools[].function.parameters Object No

The parameters the functions accepts, described as a JSON Schema object. See the guide for examples, and the JSON Schema reference for documentation about the format.

Omitting parameters defines a function with an empty parameter list.

tools[].function.strict Boolean No

Whether to enable strict schema adherence when generating the function call. If set to true, the model will follow the exact schema defined in the parameters field. Only a subset of JSON Schema is supported when strict is true. Learn more about Structured Outputs in the function calling guide.

Default value: false

tools[].type String Yes

The type of the tool. Currently, only function is supported.

Possible values:

  • "function"
metadata Object No

Set of 16 key-value pairs that can be attached to an object. This can be useful for storing additional information about the object in a structured format, and querying for objects via API or the dashboard.

Keys are strings with a maximum length of 64 characters. Values are strings with a maximum length of 512 characters.

parallel_tool_calls Boolean No

Whether to enable parallel function calling during tool use.

Default value: true

response_format Object No

An object specifying the format that the model must output.

Setting to { "type": "json_schema", "json_schema": {...} } enables Structured Outputs which ensures the model will match your supplied JSON schema. Learn more in the Structured Outputs guide.

Setting to { "type": "json_object" } enables the older JSON mode, which ensures the message the model generates is valid JSON. Using json_schema is preferred for models that support it.

reasoning_effort String No

o-series models only

Constrains effort on reasoning for reasoning models. Currently supported values are low, medium, and high. Reducing reasoning effort can result in faster responses and fewer tokens used on reasoning in a response.

Possible values:

  • "medium"
  • "low"
  • "high"

Default value: "medium"

functions[] Array No

Deprecated in favor of tools.

A list of functions the model may generate JSON inputs for.

functions[].name String Yes

The name of the function to be called. Must be a-z, A-Z, 0-9, or contain underscores and dashes, with a maximum length of 64.

functions[].description String No

A description of what the function does, used by the model to choose when and how to call the function.

functions[].parameters Object No

The parameters the functions accepts, described as a JSON Schema object. See the guide for examples, and the JSON Schema reference for documentation about the format.

Omitting parameters defines a function with an empty parameter list.

seed Integer No

This feature is in Beta. If specified, our system will make a best effort to sample deterministically, such that repeated requests with the same seed and parameters should return the same result. Determinism is not guaranteed, and you should refer to the system_fingerprint response parameter to monitor changes in the backend.

service_tier String No

Specifies the latency tier to use for processing the request. This parameter is relevant for customers subscribed to the scale tier service:

  • If set to 'auto', and the Project is Scale tier enabled, the system will utilize scale tier credits until they are exhausted.
  • If set to 'auto', and the Project is not Scale tier enabled, the request will be processed using the default service tier with a lower uptime SLA and no latency guarentee.
  • If set to 'default', the request will be processed using the default service tier with a lower uptime SLA and no latency guarentee.
  • If set to 'flex', the request will be processed with the Flex Processing service tier. Learn more.
  • When not set, the default behavior is 'auto'.

When this parameter is set, the response body will include the service_tier utilized.

Possible values:

  • "auto"
  • "flex"
  • "default"

Default value: "auto"

modalities[] Array No

Output types that you would like the model to generate. Most models are capable of generating text, which is the default:

["text"]

The gpt-4o-audio-preview model can also be used to generate audio. To request that this model generate both text and audio responses, you can use:

["text", "audio"]

logprobs Boolean No

Whether to return log probabilities of the output tokens or not. If true, returns the log probabilities of each output token returned in the content of message.

Default value: false

web_search_options Object No

This tool searches the web for relevant results to use in a response. Learn more about the web search tool.

web_search_options.user_location Object No

Approximate location parameters for the search.

web_search_options.user_location.type String Yes

The type of location approximation. Always approximate.

Possible values:

  • "approximate"
web_search_options.user_location.approximate Object Yes

Approximate location parameters for the search.

web_search_options.user_location.approximate.region String No

Free text input for the region of the user, e.g. California.

web_search_options.user_location.approximate.timezone String No

The IANA timezone of the user, e.g. America/Los_Angeles.

web_search_options.user_location.approximate.country String No

The two-letter ISO country code of the user, e.g. US.

web_search_options.user_location.approximate.city String No

Free text input for the city of the user, e.g. San Francisco.

web_search_options.search_context_size String No

High level guidance for the amount of context window space to use for the search. One of low, medium, or high. medium is the default.

Possible values:

  • "medium"
  • "low"
  • "high"

Default value: "medium"

store Boolean No

Whether or not to store the output of this chat completion request for use in our model distillation or evals products.

Default value: false

stream Boolean No

If set to true, the model response data will be streamed to the client as it is generated using server-sent events. See the Streaming section below for more information, along with the streaming responses guide for more information on how to handle the streaming events.

Default value: false

n Integer No

How many chat completion choices to generate for each input message. Note that you will be charged based on the number of generated tokens across all of the choices. Keep n as 1 to minimize costs.

Default value: 1

max_completion_tokens Integer No

An upper bound for the number of tokens that can be generated for a completion, including visible output tokens and reasoning tokens.

tool_choice Object No

Controls which (if any) tool is called by the model. none means the model will not call any tool and instead generates a message. auto means the model can pick between generating a message or calling one or more tools. required means the model must call one or more tools. Specifying a particular tool via {"type": "function", "function": {"name": "my_function"}} forces the model to call that tool.

none is the default when no tools are present. auto is the default if tools are present.

top_p Number No

An alternative to sampling with temperature, called nucleus sampling, where the model considers the results of the tokens with top_p probability mass. So 0.1 means only the tokens comprising the top 10% probability mass are considered.

We generally recommend altering this or temperature but not both.

Default value: 1

model Object Yes
frequency_penalty Number No

Number between -2.0 and 2.0. Positive values penalize new tokens based on their existing frequency in the text so far, decreasing the model's likelihood to repeat the same line verbatim.

Default value: 0

prediction Object No

Configuration for a Predicted Output, which can greatly improve response times when large parts of the model response are known ahead of time. This is most common when you are regenerating a file with only minor changes to most of the content.

messages[] Array Yes

A list of messages comprising the conversation so far. Depending on the model you use, different message types (modalities) are supported, like text, images, and audio.

logit_bias Object No

Modify the likelihood of specified tokens appearing in the completion.

Accepts a JSON object that maps tokens (specified by their token ID in the tokenizer) to an associated bias value from -100 to 100. Mathematically, the bias is added to the logits generated by the model prior to sampling. The exact effect will vary per model, but values between -1 and 1 should decrease or increase likelihood of selection; values like -100 or 100 should result in a ban or exclusive selection of the relevant token.

user String No

A unique identifier representing your end-user, which can help OpenAI to monitor and detect abuse. Learn more.

stream_options Object No

Options for streaming response. Only set this when you set stream: true.

stream_options.include_usage Boolean No

If set, an additional chunk will be streamed before the data: [DONE] message. The usage field on this chunk shows the token usage statistics for the entire request, and the choices field will always be an empty array.

All other chunks will also include a usage field, but with a null value. NOTE: If the stream is interrupted, you may not receive the final usage chunk which contains the total token usage for the request.

presence_penalty Number No

Number between -2.0 and 2.0. Positive values penalize new tokens based on whether they appear in the text so far, increasing the model's likelihood to talk about new topics.

Default value: 0

max_tokens Integer No

The maximum number of tokens that can be generated in the chat completion. This value can be used to control costs for text generated via API.

This value is now deprecated in favor of max_completion_tokens, and is not compatible with o-series models.

function_call Object No

Deprecated in favor of tool_choice.

Controls which (if any) function is called by the model.

none means the model will not call a function and instead generates a message.

auto means the model can pick between generating a message or calling a function.

Specifying a particular function via {"name": "my_function"} forces the model to call that function.

none is the default when no functions are present. auto is the default if functions are present.

top_logprobs Integer No

An integer between 0 and 20 specifying the number of most likely tokens to return at each token position, each with an associated log probability. logprobs must be set to true if this parameter is used.

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.