@@ -8,12 +8,13 @@ Expansions and Fields
8
8
``expansions ``
9
9
--------------
10
10
`Expansions `_ enable you to request additional data objects that relate to the
11
- originally returned List, Space, Tweets, or users. Submit a list of desired
12
- expansions in a comma-separated list without spaces. The ID that represents the
13
- expanded data object will be included directly in the List, Space, Tweet, or
14
- user data object, but the expanded object metadata will be returned within the
15
- ``includes `` response object, and will also include the ID so that you can
16
- match this data object to the original Space, Tweet, or user object.
11
+ originally returned List, Space, Tweets, Users, or Direct Message conversation
12
+ events. Submit a list of desired expansions in a comma-separated list without
13
+ spaces. The ID(s) that represent(s) the expanded data object(s) will be
14
+ included directly in the List, Space, Tweet, user, or event data object, but
15
+ the expanded object metadata will be returned within the ``includes `` response
16
+ object, and will also include the ID so that you can match this data object to
17
+ the original Space, Tweet, User or Direct Message conversation event object.
17
18
18
19
At this time, the only expansion available to endpoints that primarily return
19
20
List objects is ``expansions=owner_id ``. You will find the expanded user data
@@ -40,6 +41,14 @@ using this parameter:
40
41
* Attached place’s object
41
42
* Any referenced Tweets’ object
42
43
44
+ For methods that returns Direct Message conversation events, the following data
45
+ objects can be expanded using this parameter:
46
+
47
+ * The user object for the message sender.
48
+ * Attached media's object.
49
+ * Any referenced Tweet's object.
50
+ * The user object for who is joining or leaving group conversations.
51
+
43
52
At this time, the only expansion available to endpoints that primarily return
44
53
user objects is ``expansions=pinned_tweet_id ``. You will find the expanded
45
54
Tweet data object living in the ``includes `` response object.
0 commit comments