GET statuses/lookup changed the entity>urls

[LiorPlus500]

I’ve been using the “GET statuses/lookup” at my code to get full Tweet Object that I retrieve data from. The tweet contains an “App Card”.

I needed to extract the card that was used for creating the tweet.

Until recently, I saw that in the entity object I had the card URL (https://cards.twitter.com/cards/<account_id>/<card_id>), but that changed.
The URL I’m getting now seems to be related to the tweet itself (https://twitter.com/i/web/status/<tweet_id>).
When I navigate to that url I can see on the browser the card url, but I couldn’t find a way to get this data using the API.

Is there a way to know which card ID I’m using in a tweet using the API?

[andypiper]

Does the Tweet you’re retrieving contain a truncated: true value? If so, you need to use the tweet_mode=extended parameter to retrieve the complete Tweet data.

[LiorPlus500]

Hi,
You’re correct that some of the tweets had truncated: true value.

I’ve try to add the https://api.twitter.com/1.1/statuses/lookup.json?id={0}&tweet_mode=extended to my fetch request but unfortunately I’m getting event less data then what I’m getting when omitting this parameter.

Please advise

[andypiper]

Can you share a code snippet? This doesn’t make sense to me. What Tweet IDs are you fetching?

[LiorPlus500]

I’m adding both calls and responses without private data I’m deleting.

GET https://api.twitter.com/1.1/statuses/lookup.json?id=1002076683506155520 HTTP/1.1
[
	{
		"created_at": "Thu May 31 06:37:53 +0000 2018",
		"id": 1002076683506155520,
		"id_str": "1002076683506155520",
		"text": "DELETED BY AUTHER",
		"truncated": true,
		"entities":
		{
			"hashtags": [],
			"symbols": [],
			"user_mentions": [],
			"urls": [
				{
					"url": "https:\/\/t.co\/NUsLbGC55M",
					"expanded_url": "https:\/\/twitter.com\/i\/web\/status\/1002076683506155520",
					"display_url": "twitter.com\/i\/web\/status\/1\u2026",
					"indices": [117, 140]
				}
			]
		},
		"source": "\u003ca href=\"https:\/\/ads-api.twitter.com\" rel=\"nofollow\"\u003eTwitter Ads Composer\u003c\/a\u003e",
		"in_reply_to_status_id": null,
		"in_reply_to_status_id_str": null,
		"in_reply_to_user_id": null,
		"in_reply_to_user_id_str": null,
		"in_reply_to_screen_name": null,
		"user":{
			"data": "DELETED BY AUTHER"
		},			
		"geo": null,
		"coordinates": null,
		"place": null,
		"contributors": null,
		"is_quote_status": false,
		"retweet_count": 3,
		"favorite_count": 18,
		"favorited": false,
		"retweeted": false,
		"scopes":
		{
			"followers": false
		},
		"lang": "en"
	}
]

The option with the tweet_mode=extended

GET https://api.twitter.com/1.1/statuses/lookup.json?id=1002076683506155520&tweet_mode=extended HTTP/1.1
[
	{
		"created_at": "Thu May 31 06:37:53 +0000 2018",
		"id": 1002076683506155520,
		"id_str": "1002076683506155520",
		"full_text": "DELETED BY AUTHER",
		"truncated": false,
		"display_text_range": [0, 173],
		"entities":
		{
			"hashtags": [],
			"symbols": [],
			"user_mentions": [],
			"urls": []
		},
		"source": "\u003ca href=\"https:\/\/ads-api.twitter.com\" rel=\"nofollow\"\u003eTwitter Ads Composer\u003c\/a\u003e",
		"in_reply_to_status_id": null,
		"in_reply_to_status_id_str": null,
		"in_reply_to_user_id": null,
		"in_reply_to_user_id_str": null,
		"in_reply_to_screen_name": null,
		"user":
		{
			"data": "DELETED BY AUTHER"
		},
		"geo": null,
		"coordinates": null,
		"place": null,
		"contributors": null,
		"is_quote_status": false,
		"retweet_count": 3,
		"favorite_count": 18,
		"favorited": false,
		"retweeted": false,
		"scopes":
		{
			"followers": false
		},
		"lang": "en"
	}
]

[juanshishido]

Thanks for the question, @LiorPlus500.

This Tweet contains an ads card—an image app download card to be specific. When we released version 3 of the Ads API, we mentioned that we were working toward making sure all cards included a card_uri and that that should be used in favor of the preview_url (the card_uri was first introduced with version 2 of the Ads API).

The difference in usage between card_uri and preview_url is that the former is used as a request parameter value on Tweet create and the latter is appended to the Tweet’s text. It sounds like you’re used to working with the latter, where the URL has the following structure, as you mentioned: https://cards.twitter.com/cards/:account_id/:card_id.

In order to identify the card in a particular Tweet when that card was associated with the Tweet using the card_uri, you should use the include_card_uri request parameter with the value set to true. Full details in this thread. Below is an example request.

$ twurl -H api.twitter.com "/1.1/statuses/lookup.json?id=1002076683506155520&trim_user=true&include_card_uri=true"
[
  {
    "created_at": "Thu May 31 06:37:53 +0000 2018",
    "id": 1002076683506155500,
    "id_str": "1002076683506155520",
    "text": {text},
    "truncated": true,
    "entities": {
      "hashtags": [],
      "symbols": [],
      "user_mentions": [],
      "urls": [
        {
          "url": "https://t.co/NUsLbGC55M",
          "expanded_url": "https://twitter.com/i/web/status/1002076683506155520",
          "display_url": "twitter.com/i/web/status/1…",
          "indices": [
            117,
            140
          ]
        }
      ]
    },
    "source": "<a href=\"https://ads-api.twitter.com\" rel=\"nofollow\">Twitter Ads Composer</a>",
    "in_reply_to_status_id": null,
    "in_reply_to_status_id_str": null,
    "in_reply_to_user_id": null,
    "in_reply_to_user_id_str": null,
    "in_reply_to_screen_name": null,
    "user": {user},
    "geo": null,
    "coordinates": null,
    "place": null,
    "contributors": null,
    "is_quote_status": false,
    "retweet_count": 4,
    "favorite_count": 24,
    "favorited": false,
    "retweeted": false,
    "scopes": {
      "followers": false
    },
    "lang": "en",
    "card_uri": "card://1002076312343859200"
  }
]

As you can see, the card URI for the card associated with this Tweet is: card://1002076312343859200. In order to retrieve the card object, use the GET accounts/:account_id/cards endpoint and specify, card_uri=ard://1002076312343859200.

I hope this helps!