[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fSW55jH7O2CFEcWDrT4AOtEGAHkkAxC-pkw8g3qTyNyo":3,"$fZpP9UiQiDdjMs890FqnBQuChtRMMhKLcgDZuNhXHEPM":21},{"status":4,"source":5,"previous":12,"current":16,"newerSnapshotId":20,"olderSnapshotId":13},"has-previous",{"id":6,"displayName":7,"vendor":8,"kind":9,"apiType":10,"url":11},"x-api-openapi","X API","x","openapi-json","rest","https:\u002F\u002Fapi.x.com\u002F2\u002Fopenapi.json",{"id":13,"contentHash":14,"fetchedAt":15},"01KWFYJNF0VVVZYH930E6GN6MB","e94ca22d3803a52ca2d3b0ea65f021f9a30792f81944712b3dfde1b1f4fbc293","2026-07-01T23:00:12.884Z",{"id":17,"contentHash":18,"fetchedAt":19},"01KWW5Z4QP809X7M7S7P5FXHV5","42d4df1c7a449768845716343e009082f45dfb53345353303eec18a8a16b6e54","2026-07-06T17:00:14.984Z",null,{"alerts":22},[23,30,37,44,51,58,65,72,79,86,93,100],{"id":24,"severity":25,"title":26,"summary":27,"contentHash":18,"detectedAt":28,"slug":29},"01KWW5ZSC8D98VT8FSCGWQW8Z1","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","2026-07-06-x-chat-api-operationid-renamed-schema-fields-changed-removed",{"id":31,"severity":32,"title":33,"summary":34,"contentHash":14,"detectedAt":35,"slug":36},"01KWFYJRQ6CRJ3RCHAF4Z9Y19R","Additive","Add post.mention.create webhook activity type","A new webhook activity type `post.mention.create` has been added to the X API, allowing clients to subscribe to mentions being created. This is a new optional event type that expands the webhook capabilities without breaking existing integrations.","2026-07-01T23:00:16.742Z","2026-07-01-add-post-mention-create-webhook-activity-type",{"id":38,"severity":32,"title":39,"summary":40,"contentHash":41,"detectedAt":42,"slug":43},"01KVQXHFG2RTBQCEM2BS224AEB","Add like.read\u002Flike.create OAuth2 scopes and Like event support","X API adds support for likes in two subscription endpoints: `like.read` OAuth2 scope is now available on two GET endpoints, and a new `like.create` event type with corresponding `LikeWithTweetAuthor` schema is added to activity subscriptions. Additionally, the article content block schema is enhanced with detailed property definitions for cashtags, hashtags, mentions, and URLs metadata, with `additionalProperties: false` constraints added throughout for stricter validation.","bf8a8e6af90bd8b130757c9794fa6870188ded9c9cd6936b31f13aa8fa55fc14","2026-06-22T15:00:19.586Z","2026-06-22-add-like-read-like-create-oauth2-scopes-and-like-event",{"id":45,"severity":32,"title":46,"summary":47,"contentHash":48,"detectedAt":49,"slug":50},"01KTYCDYFFPXFCT976ZYRR8DVV","OAuth2 scope tightening and expansion type support","Two changes to the X API: OAuth2 scopes for two POST endpoints now require only `tweet.write` instead of `tweet.read`, `tweet.write`, and `users.read`; and a schema field supporting expansions now accepts `place` and `poll` in addition to the existing options. The scope reduction is a breaking change that narrows required auth permissions, while the new expansion types are additive.","0cd6f08161cc778220e4ec08107b53af55e71c2def73d7a952b3a7636b74070a","2026-06-12T17:00:17.263Z","2026-06-12-oauth2-scope-tightening-and-expansion-type-support",{"id":52,"severity":25,"title":53,"summary":54,"contentHash":55,"detectedAt":56,"slug":57},"01KTT6HKKZYVGVPNCEQPWQYD2R","X API v2.166: new Articles endpoints added; enum values removed from Problem type","**Two new Articles endpoints** are added (`POST \u002F2\u002Farticles\u002Fdraft` and `POST \u002F2\u002Farticles\u002F{article_id}\u002Fpublish`) along with supporting schemas (`ArticleDraftCreateRequest`, `ArticleDraftCreateResponse`, `ArticlePublishResponse`, `ArticleId`) and query parameter definitions (`ArticleExpansionsParameter`, `ArticleFieldsParameter`). Additionally, the enum on a `Problem`-related schema (likely `ResourceType` or similar) has had **`place` and `poll` removed**, leaving only `[\"user\",\"tweet\",\"media\",\"list\",\"space\"]` — clients that send or match against `\"place\"` or `\"poll\"` as valid values in that field will break.","f66a0ba723abee3d10b8e262463a8eda45f06d70cc3572248ed883412b87b835","2026-06-11T02:00:28.031Z","2026-06-11-x-api-v2-166-new-articles-endpoints-added-enum-values",{"id":59,"severity":32,"title":60,"summary":61,"contentHash":62,"detectedAt":63,"slug":64},"01KTQ6D7H8XXSV5GNJ734KKXX6","Add place and poll types to X API enum","The OpenAPI schema adds two new enum values, `place` and `poll`, to a type field, allowing clients to handle additional entity types. This is backward-compatible; existing integrations continue to work and can now optionally handle these new types.","ff5773d85442827d721019a24b8e06b3a40e704f6cbeef8c0adaae84401108ea","2026-06-09T22:00:21.288Z","2026-06-09-add-place-and-poll-types-to-x-api-enum",{"id":66,"severity":32,"title":67,"summary":68,"contentHash":69,"detectedAt":70,"slug":71},"01KTCSCF1N0PQP6FM6JDSRYNSZ","Add post event types and schemas to activity streaming","New event types `post.create` and `post.delete` are added to the activity streaming API, along with their corresponding response schemas. A new optional `includes` field for `Expansions` is also added to the streaming response. These changes are purely additive and backward-compatible with existing integrations.","1310e03050c7fcc76b1617f2558080f21e8edd8f6f6c52a188e78354310156d5","2026-06-05T21:00:20.405Z","2026-06-05-add-post-event-types-and-schemas-to-activity-streaming",{"id":73,"severity":32,"title":74,"summary":75,"contentHash":76,"detectedAt":77,"slug":78},"01KT7R0R4WHAE7YFZ78G46HWZG","Add paid_partnership field to Tweet object","The X API now exposes a new optional `paid_partnership` boolean field on Tweet objects, indicating whether a post discloses paid promotion. This is purely additive and does not affect existing integrations.","3570f4ca4923990cc1e8c73c3b61ac31b40a19fa1fb48adfc3b82155639f2993","2026-06-03T22:00:15.772Z","2026-06-03-add-paid-partnership-field-to-tweet-object",{"id":80,"severity":32,"title":81,"summary":82,"contentHash":83,"detectedAt":84,"slug":85},"01KSQVX0WT9NTGP61AE00TKCM7","Add identity_public_key_signature field to chat public key schemas","Added optional `identity_public_key_signature` field to `ChatPublicKey` and `PublicKey` schemas to carry DER-encoded signatures proving the signing key is bound to the identity key. This is a purely additive change that does not affect existing integrations.","9aa778e2afbff5697ba220ff8aef3eae1ce33776c6fad142e22c0857b6550a06","2026-05-28T18:00:17.050Z","2026-05-28-add-identity-public-key-signature-field-to-chat-public-key",{"id":87,"severity":25,"title":88,"summary":89,"contentHash":90,"detectedAt":91,"slug":92},"01KSN9GJC6NVRFNQA4WRMEB70N","max_results maximum raised from 100 to 1000, default set to 1000","The `max_results` query parameter schema has changed: its `maximum` was raised from `100` to `1000`, and a `default` of `1000` was added. This is **additive** in the sense that larger page sizes are now permitted, but it is **potentially breaking** for clients that relied on the previous cap of 100 to limit response payload size — they may now receive up to 1000 results per page if they omit `max_results` or if server-side enforcement changed. The description also now documents pagination via `pagination_token` from `meta.next_token`.","f0de79bbd20d71032028c7c264063daed67985516c67e679dc690a649d23193c","2026-05-27T18:00:25.734Z","2026-05-27-max-results-maximum-raised-from-100-to-1000-default-set-to",{"id":94,"severity":32,"title":95,"summary":96,"contentHash":97,"detectedAt":98,"slug":99},"01KSK4V1E5JDDFZY0W9P0M56PH","Add note_request_suggestions field to tweet schema","The X API OpenAPI spec adds a new `note_request_suggestions` object field to the tweet schema and includes it in the list of available tweet fields. This is a purely additive change that introduces a new optional response field containing note request suggestion data (with `source_link`, `suggestion`, and `suggestion_id` properties), allowing clients to opt-in to receiving this information without breaking existing integrations.","ed8e8a2c31dc659044d37a26eafba285e9c3fa56b87e676ba2e84ec090baa2b7","2026-05-26T22:00:17.093Z","2026-05-26-add-note-request-suggestions-field-to-tweet-schema",{"id":101,"severity":32,"title":102,"summary":103,"contentHash":104,"detectedAt":105,"slug":106},"01KS5QP4NVJ15W5QMANZZWQBJ5","Add GET endpoints for chat conversations and events","Two new read-only endpoints were added to the Chat API: `GET \u002F2\u002Fchat\u002Fconversations\u002F{id}` to retrieve conversation metadata and `GET \u002F2\u002Fchat\u002Fconversations\u002F{id}\u002Fevents` to retrieve messages and key change events. These are purely additive and require OAuth2 or UserToken scopes that already exist (`dm.read`, `tweet.read`, `users.read`).","8f8ec25f8798858fce2109552e044fc46798c4401afb83c0465c280de35749a9","2026-05-21T17:00:17.467Z","2026-05-21-add-get-endpoints-for-chat-conversations-and-events"]