Premium Search Tweets: Full-Archive API

Getting started with premium Search Tweets: Full-Archive API

⏱ 10 min read

The premium Search Tweets: Full-Archive API provides you with Tweets since the first one posted in 2006. Tweets are matched and sent back to you based on the query you specify in your request. A query is a rule in which you define what the Tweet you get back should contain. In this tutorial, we will search for Tweets originating from the Twitter account @TwitterDev in English.

The Tweets you get back in your payload can be in a data format, which provides you with the full Tweet payload, or it can be in a counts format which gives you numerical count data of matched Tweets. We will be using cURL and Twurl to make requests to the data and counts endpoints, but feel free to use your preferred method.

You will need the following:

 

Accessing the data endpoint


The data endpoint will provide us with the full Tweet payload of matched Tweets. We will use the from: and lang: operators to find Tweets originating from @TwitterDev in English. For more operators click here.

Select a method to run the API call:

cURL
cURL example
Twurl
Twurl example

cURL is a command-line tool for getting or sending files using the URL syntax.

 

Copy the following cURL request into your command line after making changes to the following:

 

  • Environment name <ENV> e.g. Prod
  • Bearer token <BEARER_TOKEN>e.g. AAAAAAAAAAAA0%2EUifi76ZC9Ub0wn...
  • fromDate and toDate e.g. "fromDate":"201802010000", "toDate":"201802282359"

      curl --request POST \
  --url https://api.twitter.com/1.1/tweets/search/fullarchive/<ENV>.json \
  --header 'authorization: Bearer <BEARER_TOKEN>' \
  --header 'content-type: application/json' \
  --data '{
                "query":"from:TwitterDev lang:en",
                "maxResults": "100",
                "fromDate":"<YYYYMMDDHHmm>", 
                "toDate":"<YYYYMMDDHHmm>"
                }'
    

This is an example cURL request. If you try to run this it will not work. 

      curl --request POST \
  --url https://api.twitter.com/1.1/tweets/search/fullarchive/prod.json \
  --header 'authorization: Bearer AAAAAAAAAAAAAAAAAAAAAMLheAAAAAAA0%2BuSeid%2BULvsea4JtiGRiSDSJSI%3DEUifiRBkKG5E2XzMDjRfl76ZC9Ub0wnz4XsNiRVBChTYbJcE3F' \
  --header 'content-type: application/json' \
  --data '{
                "query":"from:TwitterDev lang:en",
                "maxResults": "100",
                "fromDate":"201802010000", 
                "toDate":"201802282359"
                }'
    

Twurl is a cURL-like application, tailored specifically for the Twitter API.

 

Copy the following Twurl request into your command line after making changes to the following:

 

  • Environment name <ENV> e.g. Prod
  • fromDate and toDate e.g. "fromDate":"201802010000", "toDate":"201802282359"

      twurl "/1.1/tweets/search/fullarchive/<ENV>.json" -A "Content-Type: application/json" -d '{"query":"from:TwitterDev lang:en","maxResults":"100","fromDate":"<YYYYMMDDHHmm>","toDate":"<YYYYMMDDHHmm>"}' 
    

This is an example Twurl request. If you try to run this it will not work. 

      twurl "/1.1/tweets/search/fullarchive/prod.json" -A "Content-Type: application/json" -d '{"query":"from:TwitterDev lang:en","maxResults":"100","fromDate":"201802010000","toDate":"201802282359"}'
    

Data endpoint response payload

The payload you get back from your API request will appear in JSON format, as shown below.

      {
	"results": [
		{
			"created_at": "Fri Nov 02 17:18:31 +0000 2018",
			"id": 1058408022936977409,
			"id_str": "1058408022936977409",
			"text": "RT @harmophone: \"The innovative crowdsourcing that the Tagboard, Twitter and TEGNA collaboration enables is surfacing locally relevant conv…",
			"source": "<a href=\"http:\/\/twitter.com\" rel=\"nofollow\">Twitter Web Client<\/a>",
			"truncated": false,
			"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": {
				"id": 2244994945,
				"id_str": "2244994945",
				"name": "Twitter Dev",
				"screen_name": "TwitterDev",
				"location": "Internet",
				"url": "https:\/\/developer.twitter.com\/",
				"description": "Your official source for Twitter Platform news, updates & events. Need technical help? Visit https:\/\/twittercommunity.com\/ ⌨️ #TapIntoTwitter",
				"translator_type": "null",
				"protected": false,
				"verified": true,
				"followers_count": 503828,
				"friends_count": 1477,
				"listed_count": 1437,
				"favourites_count": 2199,
				"statuses_count": 3380,
				"created_at": "Sat Dec 14 04:35:55 +0000 2013",
				"utc_offset": null,
				"time_zone": null,
				"geo_enabled": true,
				"lang": "en",
				"contributors_enabled": false,
				"is_translator": false,
				"profile_background_color": "null",
				"profile_background_image_url": "null",
				"profile_background_image_url_https": "null",
				"profile_background_tile": null,
				"profile_link_color": "null",
				"profile_sidebar_border_color": "null",
				"profile_sidebar_fill_color": "null",
				"profile_text_color": "null",
				"profile_use_background_image": null,
				"profile_image_url": "null",
				"profile_image_url_https": "https:\/\/pbs.twimg.com\/profile_images\/880136122604507136\/xHrnqf1T_normal.jpg",
				"profile_banner_url": "https:\/\/pbs.twimg.com\/profile_banners\/2244994945\/1498675817",
				"default_profile": false,
				"default_profile_image": false,
				"following": null,
				"follow_request_sent": null,
				"notifications": null
			},
			"geo": null,
			"coordinates": null,
			"place": null,
			"contributors": null,
			"retweeted_status": {
				"created_at": "Tue Oct 30 21:30:25 +0000 2018",
				"id": 1057384253116289025,
				"id_str": "1057384253116289025",
				"text": "\"The innovative crowdsourcing that the Tagboard, Twitter and TEGNA collaboration enables is surfacing locally relev… https:\/\/t.co\/w46U5TRTzQ",
				"source": "<a href=\"http:\/\/twitter.com\" rel=\"nofollow\">Twitter Web Client<\/a>",
				"truncated": true,
				"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": {
					"id": 175187944,
					"id_str": "175187944",
					"name": "Tyler Singletary",
					"screen_name": "harmophone",
					"location": "San Francisco, CA",
					"url": "http:\/\/medium.com\/@harmophone",
					"description": "SVP Product at @Tagboard. Did some Data, biz, and product @Klout & for @LithiumTech; @BBI board member; @Insightpool advisor. World's worst whiteboarder.",
					"translator_type": "null",
					"protected": false,
					"verified": false,
					"followers_count": 1982,
					"friends_count": 1877,
					"listed_count": 245,
					"favourites_count": 23743,
					"statuses_count": 12708,
					"created_at": "Thu Aug 05 22:59:29 +0000 2010",
					"utc_offset": null,
					"time_zone": null,
					"geo_enabled": false,
					"lang": "en",
					"contributors_enabled": false,
					"is_translator": false,
					"profile_background_color": "null",
					"profile_background_image_url": "null",
					"profile_background_image_url_https": "null",
					"profile_background_tile": null,
					"profile_link_color": "null",
					"profile_sidebar_border_color": "null",
					"profile_sidebar_fill_color": "null",
					"profile_text_color": "null",
					"profile_use_background_image": null,
					"profile_image_url": "null",
					"profile_image_url_https": "https:\/\/pbs.twimg.com\/profile_images\/719985428632240128\/WYFHcK-m_normal.jpg",
					"profile_banner_url": "https:\/\/pbs.twimg.com\/profile_banners\/175187944\/1398653841",
					"default_profile": false,
					"default_profile_image": false,
					"following": null,
					"follow_request_sent": null,
					"notifications": null
				},
				"geo": null,
				"coordinates": null,
				"place": null,
				"contributors": null,
				"is_quote_status": false,
				"extended_tweet": {
					"full_text": "\"The innovative crowdsourcing that the Tagboard, Twitter and TEGNA collaboration enables is surfacing locally relevant conversations in real-time and enabling voters to ask questions during debates,”  -- @adamostrow, @TEGNA\nLearn More: https:\/\/t.co\/ivAFtanfje",
					"display_text_range": [
						0,
						259
					],
					"entities": {
						"hashtags": [],
						"urls": [
							{
								"url": "https:\/\/t.co\/ivAFtanfje",
								"expanded_url": "https:\/\/blog.tagboard.com\/twitter-and-tagboard-collaborate-to-bring-best-election-content-to-news-outlets-with-tagboard-e85fc864bcf4",
								"display_url": "blog.tagboard.com\/twitter-and-ta…",
								"unwound": {
									"url": "https:\/\/blog.tagboard.com\/twitter-and-tagboard-collaborate-to-bring-best-election-content-to-news-outlets-with-tagboard-e85fc864bcf4",
									"status": 200,
									"title": "Twitter and Tagboard Collaborate to Bring Best Election Content to News Outlets With Tagboard…",
									"description": "By Tyler Singletary, Head of Product, Tagboard"
								},
								"indices": [
									236,
									259
								]
							}
						],
						"user_mentions": [
							{
								"screen_name": "adamostrow",
								"name": "Adam Ostrow",
								"id": 5695942,
								"id_str": "5695942",
								"indices": [
									204,
									215
								]
							},
							{
								"screen_name": "TEGNA",
								"name": "TEGNA",
								"id": 34123003,
								"id_str": "34123003",
								"indices": [
									217,
									223
								]
							}
						],
						"symbols": []
					}
				},
				"quote_count": 0,
				"reply_count": 1,
				"retweet_count": 6,
				"favorite_count": 19,
				"entities": {
					"hashtags": [],
					"urls": [
						{
							"url": "https:\/\/t.co\/w46U5TRTzQ",
							"expanded_url": "https:\/\/twitter.com\/i\/web\/status\/1057384253116289025",
							"display_url": "twitter.com\/i\/web\/status\/1…",
							"indices": [
								117,
								140
							]
						}
					],
					"user_mentions": [],
					"symbols": []
				},
				"favorited": false,
				"retweeted": false,
				"possibly_sensitive": false,
				"filter_level": "low",
				"lang": "en"
			},
			"is_quote_status": false,
			"quote_count": 0,
			"reply_count": 0,
			"retweet_count": 0,
			"favorite_count": 0,
			"entities": {
				"hashtags": [],
				"urls": [],
				"user_mentions": [
					{
						"screen_name": "harmophone",
						"name": "Tyler Singletary",
						"id": 175187944,
						"id_str": "175187944",
						"indices": [
							3,
							14
						]
					}
				],
				"symbols": []
			},
			"favorited": false,
			"retweeted": false,
			"filter_level": "low",
			"lang": "en",
			"matching_rules": [
				{
					"tag": null
				}
			]
		}
	],
	"requestParameters": {
		"maxResults": 100,
		"fromDate": "201811010000",
		"toDate": "201811060000"
	}
}
    

Accessing the counts endpoint

With the counts endpoint, we’ll retrieve the number of Tweets originating from the @TwitterDev account in English grouped by day.

Please note that the counts endpoint is currently unavailable to premium sandbox users. 

Select a method to run the API call:

cURL
cURL example
Twurl
Twurl example

cURL is a command-line tool for getting or sending files using the URL syntax.

 

Copy the following request into your command line after making the appropriate adjustments to the following:

 

  • Environment name <ENV> e.g. Prod
  • Bearer token <BEARER_TOKEN> e.g. AAAAAAAAAAAA0%2EUifi76ZC9Ub0wn...
  • fromDate and toDate e.g. "fromDate":"201802010000", "toDate":"201802282359"

      curl --request POST \
  --url https://api.twitter.com/1.1/tweets/search/fullarchive/<ENV>/counts.json \
  --header 'authorization: Bearer <BEARER_TOKEN>' \
  --header 'content-type: application/json' \
  --data '{
                "query":"from:TwitterDev lang:en",
                "fromDate":"<YYYYMMDDHHmm>", 
                "toDate":"<YYYYMMDDHHmm>",
                "bucket": "day"
                }'
    

This is an example cURL request. If you try to run this it will not work.

      curl --request POST \
  --url https://api.twitter.com/1.1/tweets/search/fullarchive/prod/counts.json \
  --header 'authorization: Bearer AAAAAAAAAAAAAAAAAAAAAMLheAAAAAAA0%2BuSeid%2BULvsea4JtiGRiSDSJSI%3DEUifiRBkKG5E2XzMDjRfl76ZC9Ub0wnz4XsNiRVBChTYbJcE3F' \
  --header 'content-type: application/json' \
  --data '{
                "query":"from:TwitterDev lang:en",
                "fromDate":"201802010000", 
                "toDate":"201802282359"
                "bucket": "day"
                }'
    

Twurl is a cURL-like application, tailored specifically for the Twitter API.

 

Copy the following Twurl request into your command line after making changes to the following:

 

  • Environment name <ENV> e.g. Prod
  • fromDate and toDate e.g. "fromDate":"201811010000", "toDate":"201811122359"

      twurl "/1.1/tweets/search/fullarchive/<ENV>/counts.json" -A "Content-Type: application/json" -d '{"query":"from:TwitterDev lang:en","fromDate":"<YYYYMMDDHHmm>","toDate":"<YYYYMMDDHHmm>","bucket": "day"}' 
    

This is an example Twurl request. If you try to run this it will not work. 

      twurl "/1.1/tweets/search/fullarchive/prod/counts.json" -A "Content-Type: application/json" -d '{"query":"from:TwitterDev lang:en","fromDate":"201802010000","toDate":"201802282359","bucket": "day"}'
    

Counts endpoint response payload

The payload you get back from your API request will appear in JSON format, as shown below.

      {
  "results": [
    {
      "timePeriod": "201802010000",
      "count": 1
    },
    {
      "timePeriod": "201802020000",
      "count": 1
    },
    {
      "timePeriod": "201802030000",
      "count": 0
    },
    {
      "timePeriod": "201802040000",
      "count": 0
    },
    {
      "timePeriod": "201802050000",
      "count": 0
    },
    {
      "timePeriod": "201802060000",
      "count": 0
    },
    {
      "timePeriod": "201802070000",
      "count": 0
    },
    {
      "timePeriod": "201802080000",
      "count": 1
    },
    {
      "timePeriod": "201802090000",
      "count": 0
    },
    {
      "timePeriod": "201802100000",
      "count": 0
    },
    {
      "timePeriod": "201802110000",
      "count": 0
    },
    {
      "timePeriod": "201802120000",
      "count": 0
    },
    {
      "timePeriod": "201802130000",
      "count": 0
    },
    {
      "timePeriod": "201802140000",
      "count": 0
    },
    {
      "timePeriod": "201802150000",
      "count": 1
    },
    {
      "timePeriod": "201802160000",
      "count": 0
    },
    {
      "timePeriod": "201802170000",
      "count": 2
    },
    {
      "timePeriod": "201802180000",
      "count": 0
    },
    {
      "timePeriod": "201802190000",
      "count": 1
    },
    {
      "timePeriod": "201802200000",
      "count": 3
    },
    {
      "timePeriod": "201802210000",
      "count": 1
    },
    {
      "timePeriod": "201802220000",
      "count": 1
    },
    {
      "timePeriod": "201802230000",
      "count": 1
    },
    {
      "timePeriod": "201802240000",
      "count": 0
    },
    {
      "timePeriod": "201802250000",
      "count": 0
    },
    {
      "timePeriod": "201802260000",
      "count": 0
    },
    {
      "timePeriod": "201802270000",
      "count": 0
    },
    {
      "timePeriod": "201802280000",
      "count": 1
    }
  ],
  "totalCount": 14,
  "requestParameters": {
    "bucket": "day",
    "fromDate": "201802010000",
    "toDate": "201802282359"
  }
}
    

Great job! Now you've successfully accessed the premium Search Tweets: Full-archive API.

 

Referenced articles

 

Next Steps

 

Questions? Review all frequently asked questions, and get support in the support center.