TWIT_paginate_max_id | R Documentation |
These are internal functions used for pagination inside of rtweet.
TWIT_paginate_max_id(
token,
api,
params,
get_id = function(x) x$id_str,
n = 1000,
page_size = 200,
since_id = NULL,
max_id = NULL,
count_param = "count",
retryonratelimit = NULL,
verbose = TRUE
)
TWIT_paginate_cursor(
token,
api,
params,
n = 5000,
page_size = 5000,
cursor = "-1",
get_id = function(x) x$ids,
retryonratelimit = NULL,
verbose = TRUE
)
TWIT_paginate_chunked(
token,
api,
params_list,
retryonratelimit = NULL,
verbose = TRUE
)
TWIT_paginate_premium(
token,
api,
params,
n = 100,
page_size = 100,
cursor = "next",
retryonratelimit = NULL,
verbose = TRUE
)
token |
Use this to override authentication for
a single API call. In many cases you are better off changing the
default for all calls. See |
get_id |
A single argument function that returns a vector of ids given the JSON response. The defaults are chosen to cover the most common cases, but you'll need to double check whenever implementing pagination for a new endpoint. |
n |
Desired number of results to return. Results are downloaded
in pages when The Twitter API rate limits the number of requests you can perform
in each 15 minute period. The easiest way to download more than that is
to use You are not guaranteed to get exactly |
since_id |
Supply a vector of ids or a data frame of previous results to
find tweets newer than |
max_id |
Supply a vector of ids or a data frame of previous results to
find tweets older than |
retryonratelimit |
If If you expect a query to take hours or days to perform, you should not
rely solely on |
verbose |
Show progress bars and other messages indicating current progress? |
cursor |
Which page of results to return. The default will return the first page; you can supply the result from a previous call to continue pagination from where it left off. |
A list with the json output of the API.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.