X APIJuly 6, 2026

X Chat API: operationId renamed, schema fields changed/removed

BreakingBreaking change

This is a breaking change — integrations that rely on the affected behaviour will need updates before the change rolls out.

What changed

Several breaking and additive changes to the X Chat API:

operationId renamed from initializeChatConversationKeys to addConversationKeys — any SDK or code generation tooling referencing the old operation ID will break.
ChatPublicKey schema removed — clients referencing this schema directly will break; its content has been merged into the PublicKey schema.
PublicKey schema restructured: the token_map / version fields are removed; juicebox_config (a $ref) and public_key_version are added. The version enum value in the public-key fields parameter is replaced by public_key_version.
New ChatActionMessageEventSignature schema added (additive).
New conversation_id response field added to the Add Conversation Keys response (additive).
Multiple id path parameter descriptions clarified to include the hyphen-separated 1:1 conversation ID format (informational).