Create Chat Completion
Creates a chat completion of one or more messages
Creates a chat completion that generates a textual response for one or more messages using a large language model.
Request
Name of the model.
One or more chat messages.
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.
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.
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.
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.
The maximum number of tokens that can be generated in the chat completion.
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.
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.
An object specifying the format that the model must output.
Setting to { "type": "json_object" } enables JSON mode,
which guarantees the message the model generates is valid JSON.
Important: when using JSON mode, you must also instruct the model
to produce JSON yourself via a system or user message. Without this,
the model may generate an unending stream of whitespace until the
generation reaches the token limit, resulting in a long-running and
seemingly “stuck” request. Also note that the message content may
be partially cut off if finish_reason="length", which indicates the
generation exceeded max_tokens or the conversation exceeded the max context length.
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.
Up to 4 sequences where the API will stop generating further tokens.
If set, partial message deltas will be sent. Tokens will be sent as
data-only server-sent events as they become available, with the stream
terminated by a data: [DONE] message.
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.
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.
Response
Returned when stream is false or not set.
A unique identifier for the chat completion.
A list of chat completion choices. Can be more than one if n is greater than 1.
The Unix timestamp (in seconds) of when the chat completion was created.
The model used for the chat completion.
This fingerprint represents the backend configuration that the model runs with.
Can be used in conjunction with the seed request parameter to understand
when backend changes have been made that might impact determinism.
The object type, which is always chat.completion.
Usage statistics for the completion request.
Stream Response
Returned when stream is true.
A unique identifier for the chat completion. Each chunk has the same ID.
A list of chat completion choices. Can be more than one if n is greater than 1.
Can also be empty for the last chunk.
The Unix timestamp (in seconds) of when the chat completion was created. Each chunk has the same timestamp.
The model used for the chat completion.
This fingerprint represents the backend configuration that the model runs with.
Can be used in conjunction with the seed request parameter to understand
when backend changes have been made that might impact determinism.
The object type, which is always chat.completion.chunk.
it contains a null value except for the last chunk which contains the token usage statistics for the entire request.
Was this page helpful?