Update Chat Completion

Modify a stored chat completion. Only Chat Completions that have been created with the store parameter set to true can be modified. Currently, the only supported modification is to update the metadata field.

Options

Completion Id

The ID of the chat completion to update.

Body

Result Format

Specify how the response should be mapped to the table output. The following formats are available:

Structured Table: Returns a parsed table with data split into rows and columns.

• Id: A unique identifier for the chat completion.
• Choices: A list of chat completion choices. Can be more than one if n is greater than 1.
• Created: The Unix timestamp (in seconds) of when the chat completion was created.
• Model: The model used for the chat completion.
• Service Tier:

  Specifies the processing type used for serving the request.

  • If set to 'auto', then the request will be processed with the service tier configured in the Project settings. Unless otherwise configured, the Project will use 'default'.
  • If set to 'default', then the request will be processed with the standard pricing and performance for the selected model.
  • If set to 'flex' or 'priority', then the request will be processed with the corresponding service tier.
  • When not set, the default behavior is 'auto'.

  When the service_tier parameter is set, the response body will include the service_tier value based on the processing mode actually used to serve the request. This response value may be different from the value set in the parameter.

• System Fingerprint:

  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.

• Object: The object type, which is always chat.completion.
• Usage: Usage statistics for the completion request.

Raw Response: Returns the raw response in a single row with the following columns:

• body: Response body
• status: HTTP status code

Views

This node has no views

Workflows

• No workflows found

Links

• No links available

Developers