fetch_reviews: Fetch all structured reviews data from hundreds of review...

In hrbrmstr/webhose: Tools to Work with the 'webhose.io' 'API'

Description

Fetch all structured reviews data from hundreds of review sites

Usage

fetch_reviews(query, sort = "relevancy", ts = (Sys.time() - (3 * 24 * 60 *
  60)), order = "desc", accuracy_confidence = NULL, highlight = FALSE,
  pre_alloc_max = 30, quiet = !interactive(),
  token = Sys.getenv("WEBHOSE_TOKEN"), ...)

Arguments

query	A string query containing the filters that define which reviews will be returned.
sort	By default the results are sorted by relevancy. Acceptable values are "relevancy", "social.facebook.likes", "social.facebook.shares", "social.facebook.comments", "social.gplus.shares", "social.pinterest.shares", "social.linkedin.shares", "social.stumbledupon.shares", "social.vk.shares", "replies_count", "participants_count", "spam_score", "performance_score", "published", "thread.published", "domain_rank", "ord_in_thread", "rating".
ts	A timestamp to start the search from. If a POSIXct is passed in, it will be converted to the necessary value in milliseconds. Default is previous 3 days.
order	asc (ascending) or desc (descending, default) sort order for results
accuracy_confidence	NULL or high. If high, return only posts with high extraction accuracy, but removes about 30 lower confidence).
highlight	FALSE or TRUE. Return the fragments in the post that matched the textual boolean query. The matched keywords will be surrounded by <em/> tags. Default: FALSE
pre_alloc_max	If you know the approximate number of API calls that will need to be made to retrieve a full set of records for a query, use that number here (defaults to 30, which is enough space to hold 3,000 total records if each API call returns 100). This helps pre-allocate space and avoid copying interim buffers as the result set expands.
quiet	By default, calls in interactive sessions will return fetch status updates. Use TRUE to suppress these messages.
token	Your private access token. You get a unique access token when you sign up. Store it in an environment variable WEBHOSE_TOKEN (usually in ~/.Renviron) or provide it directly.
...	other parameters passed on (eventually) to httr::GET()

References

webhose API

Examples

## Not run: 
res <- fetch_reviews("site_category:travel rating:<3 (bug OR roach OR cockroach)")

## End(Not run)

hrbrmstr/webhose documentation built on May 30, 2019, 6:56 p.m.