safety_identifier request field You can now send safety_identifier , an opaque end-user identifier assigned by your application, on Chat Completions, the Responses API, deferred chat completions, the Batch API, and the gRPC GetCompletionsRequest . It lets SpaceXSI attribute a policy violation to one of your end users rather than to your API key. The legacy user field is still accepted. See the Security FAQ . September 21
Open original sourcesafety_identifier request field
safety_identifier request field You can now send safety_identifier , an opaque end-user identifier assigned by your application, on Chat Completions, the Responses API, deferred chat completions, the Batch API, and the gRPC GetCompletionsRequest . It lets SpaceXSI attribute a policy violation to one of your end users rather than to your API key. The legacy user field is still accepted. See the Security FAQ . September 21
Evidence chain
safety_identifier request field You can now send safety_identifier , an opaque end-user identifier assigned by your application, on Chat Completions, the Responses API, deferred chat completions, the Batch API, and the gRPC GetCompletionsRequest . It lets SpaceXSI attribute a policy violation to one of your end users rather than to your API key. The legacy user field is still accepted. See the Security FAQ . September 21
Open original sourcesafety_identifier request field You can now send safety_identifier , an opaque end-user identifier assigned by your application, on Chat Completions, the Responses API, deferred chat completions, the Batch API, and the gRPC GetCompletionsRequest . It lets SpaceXSI attribute a policy violation to one of your end users rather than to your API key. The legacy user field is still accepted. See the Security FAQ . September 21
Open original sourcesafety_identifier request field You can now send safety_identifier , an opaque end-user identifier assigned by your application, on Chat Completions, the Responses API, deferred chat completions, the Batch API, and the gRPC GetCompletionsRequest . It lets SpaceXSI attribute a policy violation to one of your end users rather than to your API key. The legacy user field is still accepted. See the Security FAQ . September 21
Open original sourceExternal discussion
No reviewed external discussion has been linked yet. This does not change the evidence confidence.