New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

oauth1.0_token or oauth2.0_token for vimeo? #491

braggbear opened this Issue Oct 24, 2017 · 2 comments


None yet
3 participants

braggbear commented Oct 24, 2017

In the vimeo exampl, oauth1.0_token is used but I have read elsewhere that we should be using oauth2.0_token. Should we use 2.0, not 1.0? If so, could you update the vimeo example to ensure I have it right? Thank you!!!


This comment has been minimized.

smithjd commented Feb 2, 2018

The oauth 1.0 access point no longer works, so oauth2.0 is much needed! -- Please!

Could this this attempt (#485) be a hint?


This comment has been minimized.

smithjd commented Feb 21, 2018

With a few caveats, here is a work-around, using the reticulate package and examples here:


# load python modules previously installed with pim:
os <- import("os")
sys <- import("sys")
vimeo <- import("vimeo")
json <- import("json")

v <- vimeo$VimeoClient(
  token = Sys.getenv("vimeo_api_access_token"),
  key = Sys.getenv("vimeo_api_key"),
  secret = Sys.getenv("vimeo_api_secret")

album <- v$get("/me/albums?per_page=100&fields=modified_time,name,duration,link,created_time")
album_json <- album$json()


  • download Python modules vimeo and json
  • obtain token, key, and secret from vimeo
  • album_json is an R list that you can parse using R's various JSON methods.

@hadley hadley added the wip label Nov 22, 2018

hadley added a commit to peterhartman/httr that referenced this issue Dec 4, 2018

@hadley hadley closed this in d17a69a Dec 4, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment