Skip to content
Back

xAIGrok API

safety\_identifier request field

AI summary

Written by AI from the official notes. Check them for exact details.

A new safety_identifier field has been added for better tracking of policy violations.

  • New safety_identifier for end-user tracking on various APIs.
  • Allows attribution of policy violations to end users.
  • Legacy user field remains accepted.

Why it matters: Developers using Grok should implement this for improved compliance tracking.

Official notes on docs.x.ai

Full release notes

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.