Token

Token-class

Token1.0

Token2.0

TokenServiceAccount

These objects represent the complete set of data needed for OAuth access:
an app, an endpoint, cached credentials and parameters. They should be
created through their constructor functions <code><a href="/link/oauth1.0_token?package=httr&version=1.0.0" rd-options="" data-mini-rdoc="httr::oauth1.0_token">oauth1.0_token</a></code>
and <code><a href="/link/oauth2.0_token?package=httr&version=1.0.0" rd-options="" data-mini-rdoc="httr::oauth2.0_token">oauth2.0_token</a></code>.

datasets

internal

Useful tools for working with HTTP organised by HTTP verbs
    (GET(), POST(), etc). Configuration functions make it easy to control
    additional request components (authenticate(), add_headers() and so on).

Hadley Wickham

httr

Tools for Working with URLs and HTTP

Token-class function

format

<ul><li><code>cache()</code>: caches token to disk</li><li><code>sign(method, url)</code>: returns list of url and config</li><li><code>refresh()</code>: refresh access token (if possible)</li><li><code>validate()</code>: TRUE if the token is still valid, FALSE otherwise</li></ul>

Methods

OAuth tokens are cached on disk in a file called <code>.httr-oauth</code>
saved in the current working directory. Caching is enabled if:<ul><li>The session is interactive, and the user agrees to it, OR</li><li>The<code>.httr-oauth</code>file is already present, OR</li><li><code>getOption("httr_oauth_cache")</code>is<code>TRUE</code></li></ul>You can suppress caching by setting the <code>httr_oauth_cache</code> option to
<code>FALSE</code>.Tokens are cached based on their endpoint and parameters.The cache file should not be included in source code control or R packages
(because it contains private information), so httr will automatically add
the appropriate entries to `.gitignore` and `.Rbuildignore` if needed.

Token-class: OAuth token objects.

Description

Usage

Arguments

format

Methods

Caching