The Chat Completions create method labels user as Deprecated. The Responses create method says the same field is being replaced. Neither page gives a day when user stops working.
The Chat Completions create reference prints Deprecated user, then this sentence: This field is being replaced by safety_identifier and prompt_cache_key. Use prompt_cache_key instead to maintain caching optimizations. On that page, prompt_cache_key says it is used by OpenAI to cache responses for similar requests to optimize cache hit rates, and that it replaces the user field. safety_identifier says it is a stable identifier used to help detect users of your application that may be violating OpenAI's usage policies. The IDs should uniquely identify each user, with a maximum length of 64 characters. The page recommends hashing their username or email address, in order to avoid sending identifying information. The Responses create reference prints the same replacement sentence for user. It does not print the word Deprecated on that field. Its prompt_cache_key line also says the field replaces the user field. Its safety_identifier line says the maximum length is 128 characters, and it also recommends hashing a username or email address. The deprecations page, checked 2026-10-26, does not list the user field and does not give a removal date. The API changelog mentions safety_identifier for the Safety Usage Dashboard. It does not say the user field is deprecated and it does not give a removal date. The row below is a current model id whose create method documents the field. It is not a shutdown of that model.
Source: Create chat completion, checked October 26, 2026.
Affected models
A current model id. The field is on the create method, not a shutdown of this id.
The Chat Completions and Responses create methods document user on the request. This row is not a gpt-5.5 shutdown.
Fix
Raw SDK
Send safety_identifier and prompt_cache_key instead of user. The Chat Completions page says to use prompt_cache_key to maintain caching optimizations, and safety_identifier to identify an end user. Hash the username or email. Chat Completions says the safety identifier maximum length is 64 characters. Responses says 128 characters. These samples do not include a key.
This page does not show an AI SDK call. The Chat Completions and Responses create references say to send safety_identifier and prompt_cache_key instead of user.
safety_identifier and prompt_cache_key. The Chat Completions create reference says user is being replaced by those two fields, and to use prompt_cache_key to maintain caching optimizations. safety_identifier is the stable id for abuse detection. Hash the username or email.
When does user stop working?
The deprecations page, checked 2026-10-26, does not list this field and does not give a removal date. The API changelog does not give one either.
Does Responses use the same replacement?
The Responses create reference prints the same replacement sentence. It does not print the word Deprecated on user. Its safety_identifier maximum length is 128 characters. Chat Completions says 64 characters.