The pushshift.io Reddit API was designed and created by the /r/datasets mod team to help provide enhanced functionality and search capabilities for searching Reddit comments and submissions. The project lead, /u/stuck_in_the_matrix, is the maintainer of the Reddit comment and submissions archives located at https://files.pushshift.io.
This RESTful API gives full functionality for searching Reddit data and also includes the capability of creating powerful data aggregations. With this API, you can quickly find the data that you are interested in and find fascinating correlations.
There are two main ways of accessing the Reddit comment and submission database. One is by using the API directly via https://api.pushshift.io/ and the other is through accessing the back-end Elasticsearch search engine via https://elastic.pushshift.io/ This document will explain both approaches and give examples on how to effectively use the API. This document will also explore the use of the API parameters to utilize more focused searches.
Using the https://api.pushshift.io endpoints
There are two main endpoints used to search all publicly available comments and submissions on Reddit:
- /reddit/search/comment
- /reddit/search/submission
In the next section, we will explore how to perform more effective searches using the comment search endpoint.
To search for comments, use the https://api.pushshift.io/reddit/search/comment/ endpoint. Let's start with a few examples and then go over the various parameters available when using this endpoint. One of the simplest searches is using just the q parameter. The q parameter is used to search for a specific word or phrase. Here is an example:
Search for the most recent comments mentioning the word "science"
https://api.pushshift.io/reddit/search/comment/?q=science
This will search the most recent comments with the term "science" in the body of the comment. This search is not case-sensitive, so it will find any occurence of the term "science" regardless of capitalization. The API defaults to sorting by recently made comments first. After performing this search, 25 results are returned. This is the default size for searches and can be adjusted using the size parameter. This will be discussed in further detail in the parameters section. Data is returned in JSON format and actual search results are included in the "data" key. There is also a "metadata" key that gives additional information about the search including total number of results found, how long the search took to process, etc. If aggregations are requested, all aggregation data is returned under the aggs key.
There are numerous additional parameters that can be used when performing a comment search. Let's go over them and provide examples for each.
| Parameter | Description | Default | Accepted Values |
|---|---|---|---|
| q | Search term. | N/A | String / Quoted String for phrases |
| ids | Get specific comments via their ids | N/A | Comma-delimited base36 ids |
| size | Number of results to return | 25 | Integer <= 500 |
| fields | One return specific fields (comma delimited) | All Fields Returned | string or comma-delimited string |
| sort | Sort results in a specific order | "desc" | "asc", "desc" |
| sort_type | Sort by a specific attribute | "created_utc" | "score", "num_comments", "created_utc" |
| aggs | Return aggregation summary | N/A | ["author", "link_id", "created_utc", "subreddit"] |
| author | Restrict to a specific author | N/A | String |
| subreddit | Restrict to a specific subreddit | N/A | String |
| after | Return results after this date | N/A | Epoch value or Integer + "s,m,h,d" (i.e. 30d for 30 days) |
| before | Return results before this date | N/A | Epoch value or Integer + "s,m,h,d" (i.e. 30d for 30 days) |
| frequency | Used with the aggs parameter when set to created_utc | N/A | "second", "minute", "hour", "day" |
| metadata | display metadata about the query | false | "true", "false" |
You can retrieve comments directly by using the ids parameter. To get a batch of comments by their id, use the following example:
Retrieve three comments using their base 36 id values
https://api.pushshift.io/reddit/comment/search?ids=dlrezc8,dlrawgw,dlrhbkq
There are quite a few parameters to review, so let's start by providing some more complex examples and how to use the parameters above. Let's continue with the previous example above and expand on our "science" keyword search. What if we wanted to search for the term "science" but restrict it to a specific subreddit? By using the subreddit parameter, we can do that:
Search for the most recent comments mentioning the word "science" within the subreddit /r/askscience
https://api.pushshift.io/reddit/search/comment/?q=science&subreddit=askscience
This will return 25 comments containing the term "science" but only from the /r/askscience subreddit. Since we didn't ask for a specific sort method, the most recent comments are returned (the sort parameter defaults to "desc"). What if we wanted the first comment ever to /r/askscience that mentioned the word "science"? We could use the sort and size parameters to handle that.
Search for the most recent comments mentioning the word "science" within the subreddit /r/askscience
https://api.pushshift.io/reddit/search/comment/?q=science&subreddit=askscience&sort=asc&size=1
This is the result:
{
"data": [
{
"author": "MockDeath",
"author_flair_css_class": null,
"author_flair_text": null,
"body": "Knowing more would definitely help. I guess all you can do is find out if they know the basics like you said then take it from there. That CO\u00b2 has the carbon turned to the isotope carbon14 in the upper atmosphere by cosmic radiation. This causes a specific percentage of carbon in the atmosphere to be carbon14.\n\nNow we are carbon based life forms and we have to get the carbon we are built out of from some where. We get it from eating plants, and the plants get it from absorbing CO\u00b2 from the air. So so long as we are alive, we uptake new carbon14. So this gives you a pretty good base line for dating.\n\nNow to fight arguments against carbon dating you could use the example of how we can see proton collisions in the LHC for sensitivity of our equipment. Nuclear decay is very accurate in how fast it happens, this is why atomic clocks work to a much higher degree of accuracy than other methods of time keeping. Also, you might want to make a general appeal for science. Science works, that is why we have TV's, robots, particle accelerators, satellites, computers, MRI and CAT scanners, nuclear power, etc etc. Scientists are not just willy nilly making shit up, or these kinds of things wouldn't work.",
"created_utc": 1270637661,
"id": "c0nn9iq",
"link_id": "t3_bne3u",
"parent_id": "t1_c0nn5ux",
"score": 2,
"subreddit": "askscience",
"subreddit_id": "t5_2qm4e"
}
],
"metadata": {
"execution_time_milliseconds": 30.52,
"results_returned": 1,
"shards": {
"failed": 0,
"successful": 36,
"total": 36
},
"size": 1,
"sort": "asc",
"sort_type": "created_utc",
"timed_out": false,
"total_results": 134785,
"version": "v3.0"
}
}
From the result returned, we can see that the first comment ever made to /r/askscience mentioning "science" happened on epoch date 1270637661, which translates to Wednesday, April 7, 2010 10:54:21 AM (GMT). Let's quickly go over the metadata pieces. We can see that the execution time for this search was around 30 milliseconds. There were a total of 36 shards searched and all were successful. The search did not time out (timed_out parameter) which is good. This is an attribute you may want to check if you use the API programmatically as some searches that are more complicated may sometimes time out. The total_results value is 134,785. This tells us the total number of comments in /r/askscience that mention the word science. Since we did not use the before or after parameters, this number represents the entirety of the comments made to /r/askscience.
Let's continue by using additional parameters to highlight the power of the search API. The before and after parameters allow you to restrict the time-frame for the search by giving an epoch timestamp for both. However, the API also understands more human-like values for the before and after parameters. You can use a number followed by the characters s,m,h,d (which stand for second, minute, hour and day) to limit the time-frame as well. Let's run through some examples.
If you wanted to do a search for "Rome" in the subreddit /r/askhistorians but limit it only to the past 30 days, you could use the after parameter with the value 30d (30 days).
Search the subreddit /r/askhistorians for comments mentioning Rome within the past 30 days
https://api.pushshift.io/reddit/search/comment/?q=rome&subreddit=askhistorians&after=30d
What if there was a recent news story three days ago, but we wanted to limit the search window between 4 days ago and 2 days ago? We could use both the before and after parameter to do so. In the next example, we will search for comments mentioning Trump that were made between 4 and 2 days ago and sort by ascending.
Search all subreddits for the term "Trump" and return comments made between 2 and 4 days ago
https://api.pushshift.io/reddit/search/comment/?q=trump&after=4d&before=2d&sort=asc
Let's say you wanted to do a search for the last 150 comments, but you only need the author and body fields returned for each comment. Using the fields parameter, you can tell the API which pieces of information you want to filter. This is primarily to help reduce bandwidth if you are making a lot of requests and only need specific fields returned.
Here is an example using the fields parameter to search for the past 150 comments that mention "government" and only returning the author and body fields:
Search all subreddits for the term "government" and return comments with only the body and author keys
https://api.pushshift.io/reddit/search/comment/?q=government&size=150&fields=body,author
Using one of the examples above that searched for the first occurrence of the word "science" in the subreddit /r/askscience, we saw that the author of the comment was "MockDeath." What if we wanted to get the first 100 comments that "MockDeath" made to Reddit? We can use the author parameter, along with the sort and size parameters.
Search all subreddits and get the first 100 comments ever made by the user /u/MockDeath
https://api.pushshift.io/reddit/search/comment/?author=MockDeath&sort=asc&size=100
Aggregations is a powerful method to give summary data for a search. Using the aggs parameter, we can quickly create facets around specific parameters and see how data changes over time. The aggs parameter for comment searches accepts the following values: author, subreddit, reated_utc and link_id. We can do a lot of very cool things using this parameter, so let's dive into some examples.
Let's say we wanted to see the frequency of usage for the term "Trump" over time. We'd like to be able to see how many comments were posted per hour over the past 7 days for this term. Using aggregations and the aggs parameter, we can get that data quickly. Here's an example using this criteria:
Create a time aggregation using the term trump to show the number of comments mentioning trump each hour over the past 7 days
We used the frequency parameter along with the aggs parameter to create hourly buckets to show the total number of comments mentioning Trump over the past 7 days. The size parameter was set to 0 because we are only interested in getting aggregation data and not comment data. The aggregation data is returned in the response under the key aggs -> created_utc. Here is a snippet of the first part of the return:
{
"aggs": {
"created_utc": [
{
"doc_count": 685,
"key": 1502406000
},
{
"doc_count": 1238,
"key": 1502409600
},
{
"doc_count": 1100,
"key": 1502413200
},
The doc_count value is the total number of comments containing the term "trump." The key value is the epoch time for that particular bucket. In this example, the first bucket has an epoch time of 1502406000 which corresponds to Thursday, August 10, 2017 11:00:00 PM. This key value is the beginning time of the bucket, so in this example, 685 comments contain the term "trump" between the time Thursday, August 10, 2017 11:00:00 PM and Thursday, August 10, 2017 12:00:00 PM. The frequency parameter allows you to create buckets per second, minute, hour, day, week, month, year. Using this aggregation, you could use the data to create a chart (i.e. Highcharts) and graph the activity of comments for specific terms, authors, subreddits, etc. This is an extremely powerful data analysis tool.
What if you wanted to not only get the frequency of specific comment terms over time, but also wanted to see which subreddits were the most popular for a given term over that time period? Here's an example of using the aggs parameters to show which subreddits had the most activity for a specific term.
Create a subreddit aggregation using the term trump to show the top subreddits mentioning trump over the past 7 days
https://api.pushshift.io/reddit/search/comment/?q=trump&after=7d&aggs=subreddit&size=0
Here is a snippet of the result:
{
"aggs": {
"subreddit": [
{
"bg_count": 66,
"doc_count": 44,
"key": "lovetrumpshaters",
"score": 0.6666666666666666
},
{
"bg_count": 20,
"doc_count": 9,
"key": "Denmark_Uncensored",
"score": 0.45
},
{
"bg_count": 51,
"doc_count": 16,
"key": "WhoRedditHatesNow",
"score": 0.3137254901960784
},
The subreddit aggregation will return the total number of comments in that subreddit that mention the query term (doc_count) as well as the total number of comments made to that subreddit during that time period (bg_count). This not only will show you which subreddits mentioned Trump the most often, but it also gives you normalized results so that you can also see what percentage of that subreddit's comments contained the search term. If you were to simply rank the subreddits by which subreddits mentioned the search term "trump" the most often, the results would be biased towards subreddits that also contain the most activity in general. Using this approach, you can see both the raw count and also the normalized data.
The API also allows aggregations on link_id, which is another very powerful method to see which submissions are the most popular based on a specific search term. Continuing with the examples above, let's give a scenario where this would be extremely helpful. Within the past 24 hours, numerous big stories have dropped concerning Donald Trump. You would like to use the API to see which submissions are related to Trump based on the number of comments mentioning him within the submissions. We can again use the aggs parameter and set it to link_id to get this information quickly. Let's proceed with another example:
Show submissions made within the past 24 hours that mention trump often in the comments
https://api.pushshift.io/reddit/search/comment/?q=trump&after=24h&aggs=link_id&size=0
This will return under the aggs -> link_id key an array of submission objects. The doc_count gives the total number of comments for each submission that mention the search term ("trump") and the bg_count give the total number of comments made to that submission. This is a great way to quickly find submissions that are "hot" based on a specific search term or phrase.
The API also allows you to create aggregations on authors so you can quickly see which authors make the most comments for a specific search term. Here is an example of using the author aggregation:
Show the top authors mentioning the term "Trump" over the past 24 hours
https://api.pushshift.io/reddit/search/comment/?q=trump&after=24h&aggs=author&size=0
{
"aggs": {
"author": [
{
"doc_count": 605,
"key": "grrrrreat"
},
{
"doc_count": 329,
"key": "AutoModerator"
},
{
"doc_count": 168,
"key": "autotldr"
},
{
"doc_count": 73,
"key": "SnapshillBot"
},
The author aggregation will show you which authors make the most comments containing a specific query term. From the example above, a lot of the top authors mentioning the term "Trump" are actually bots.
Using the aggs parameter, you can combine multiple aggregations and get a lot of facet data for a specific term. Using the examples above, we can combine all of the calls into one call and show the top submissions over the past 24 hours, the frequency of comments per hour mentioning Trump, the top authors posting about Trump and the top subreddits that have had comments made mentioning Trump.
Show aggregations for authors, submissions, subreddits and time frequency for the term "Trump" over the past 24 hours
To search for submissions, use the endpoint https://api.pushshift.io/reddit/search/submission/ endpoint. Let's start with a few examples and then go over the various parameters available when using this endpoint. Do to a simple search, the q parameter is used to search for a specific word or phrase. Here is an example:
Search for the most recent submissions mentioning the word "science"
https://api.pushshift.io/reddit/search/submission/?q=science
This will search for the most recent submissions with the word science in the title or selftext. The search is not case-sensitive, so it will find any occurence of science regardless of capitalization. The API defaults to sorting by the most recently made submissions first. After running this search, 25 results are returned. This is the default size for searches and can be changed by using the size parameter. This will be discussed in further detail in the parameters section. Data is returned in JSON format and results are included in the "data" key.
There are numerous additional parameters that can be used when performing a submission search. Let's go over each of them now and provide examples for each one.
| Parameter | Description | Default | Accepted Values |
|---|---|---|---|
| ids | Get specific submissions via their ids | N/A | Comma-delimited base36 ids |
| q | Search term. Will search ALL possible fields | N/A | String / Quoted String for phrases |
| q:not | Exclude search term. Will exclude these terms | N/A | String / Quoted String for phrases |
| title | Searches the title field only | N/A | String / Quoted String for phrases |
| title:not | Exclude search term from title. Will exclude these terms | N/A | String / Quoted String for phrases |
| selftext | Searches the selftext field only | N/A | String / Quoted String for phrases |
| selftext:not | Exclude search term from selftext. Will exclude these terms | N/A | String / Quoted String for phrases |
| size | Number of results to return | 25 | Integer <= 500 |
| fields | One return specific fields (comma delimited) | All Fields | String or comma-delimited string (Multiple values allowed) |
| sort | Sort results in a specific order | "desc" | "asc", "desc" |
| sort_type | Sort by a specific attribute | "created_utc" | "score", "num_comments", "created_utc" |
| aggs | Return aggregation summary | N/A | ["author", "link_id", "created_utc", "subreddit"] |
| author | Restrict to a specific author | N/A | String or comma-delimited string (Multiple values allowed) |
| subreddit | Restrict to a specific subreddit | N/A | String or comma-delimited string (Multiple values allowed) |
| after | Return results after this date | N/A | Epoch value or Integer + "s,m,h,d" (i.e. 30d for 30 days) |
| before | Return results before this date | N/A | Epoch value or Integer + "s,m,h,d" (i.e. 30d for 30 days) |
| score | Restrict results based on score | N/A | Integer or > x or < x (i.e. score=>100 or score=<25) |
| num_comments | Restrict results based on number of comments | N/A | Integer or > x or < x (i.e. num_comments=>100) |
| over_18 | Restrict to nsfw or sfw content | both allowed | "true" or "false" |
| is_video | Restrict to video content | both allowed | "true" or "false" |
| locked | Return locked or unlocked threads only | both allowed | "true" or "false" |
| stickied | Return stickied or unstickied content only | both allowed | "true" or "false" |
| spoiler | Exclude or include spoilers only | both allowed | "true" or "false" |
| contest_mode | Exclude or include content mode submissions | both allowed | "true" or "false" |
| frequency | Used with the aggs parameter when set to created_utc | N/A | "second", "minute", "hour", "day" |
| metadata | display metadata about the query | false | ["true", "false"] |
This call is very helpful when used along with Reddit's API. When there are large submissions with thousands of comments, it is often difficult to get all the comment ids for a submission. This call will return an array of comment ids when a submission id is passed to it. The endpoint is: https://api.pushshift.io/reddit/submission/comment_ids/{base36 submission id}
This call will return a data key with an array of comment ids. You can then retrieve the actual comment information from this API or the Reddit API. If the submission is fairly new, it is better to use the Reddit API to get the most current score for the comments.
Retrieve all comment ids for a submission object
https://api.pushshift.io/reddit/submission/comment_ids/6uey5x
| Endpoint | Description | Status |
|---|---|---|
| /reddit/search/comment/ | Search Reddit Comments | Active |
| /reddit/search/submission/ | Search Reddit Submissions | Active |
| /reddit/submission/comment_ids/{base36-submission-id} | Retrieve comment ids for a submission object | Active |
| /reddit/analyze/user/{author-name} | Analyze a Reddit user's activity | In Development |
| /reddit/term/frequency/{term} | Analyze a term based on activity | In Development |
| /reddit/search/all/ | Search Both Comment and Submissions | In Development |
| /reddit/trending/people | Find out who is trending on Reddit | In Development |
| /reddit/search/links | Find relevent links being shared on Reddit | In Development |