[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-x-api-openapi-2026-07-06-x-chat-api-operationid-renamed-schema-fields-changed-removed":3},{"source":4,"alert":11},{"id":5,"displayName":6,"vendor":7,"kind":8,"apiType":9,"url":10},"x-api-openapi","X API","x","openapi-json","rest","https:\u002F\u002Fapi.x.com\u002F2\u002Fopenapi.json",{"id":12,"slug":13,"severity":14,"title":15,"summary":16,"detectedAt":17},"01KWW5ZSC8D98VT8FSCGWQW8Z1","2026-07-06-x-chat-api-operationid-renamed-schema-fields-changed-removed","Breaking","X Chat API: operationId renamed, schema fields changed\u002Fremoved","Several breaking and additive changes to the X Chat API:\n\n- **`operationId` renamed** from `initializeChatConversationKeys` to `addConversationKeys` — any SDK or code generation tooling referencing the old operation ID will break.\n- **`ChatPublicKey` schema removed** — clients referencing this schema directly will break; its content has been merged into the `PublicKey` schema.\n- **`PublicKey` schema restructured**: the `token_map` \u002F `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`.\n- **New `ChatActionMessageEventSignature` schema** added (additive).\n- **New `conversation_id` response field** added to the Add Conversation Keys response (additive).\n- Multiple `id` path parameter descriptions clarified to include the hyphen-separated 1:1 conversation ID format (informational).","2026-07-06T17:00:36.616Z"]