Build a request, using knowledge of the Drive v3 API from its Discovery Document. Most users should, instead, use higher-level wrappers that facilitate common tasks, such as uploading or downloading Drive files. The functions here are intended for internal use and for programming around the Drive API.
request_generate() lets you provide the bare minimum of input.
It takes a nickname for an endpoint and:
Uses the API spec to look up the
method, and base URL.
params for validity and completeness with respect to the
endpoint. Separates parameters into those destined for the body, the query,
and URL endpoint substitution (which is also enacted).
Adds an API key to the query if and only if
token = NULL.
supportsAllDrives = TRUE to the query if the endpoint requires.
Character. Nickname for one of the selected Drive v3 API
endpoints built into googledrive. Learn more in
Named list. Parameters destined for endpoint URL substitution, the query, or the body.
API key. Needed for requests that don't contain a token. The need
for an API key in the absence of a token is explained in Google's document
Credentials, access, security, and identity.
In order of precedence, these sources are consulted: the formal
key parameter in
params, a user-configured API key fetched
drive_api_key(), a built-in key shipped with googledrive. See
drive_auth_configure() for details on a user-configured key.