request_make | R Documentation |
Intended primarily for internal use in client packages that provide
high-level wrappers for users. request_make()
does relatively little:
Calls an HTTP method.
Adds a user agent.
Enforces "json"
as the default for encode
. This differs from httr's
default behaviour, but aligns better with Google APIs.
Typically the input is created with request_build()
and the output is
processed with response_process()
.
request_make(x, ..., encode = "json", user_agent = gargle_user_agent())
x |
List. Holds the components for an HTTP request, presumably created
with |
... |
Optional arguments passed through to the HTTP method. Currently neither gargle nor httr checks that all are used, so be aware that unused arguments may be silently ignored. |
encode |
If the body is a named list, how should it be encoded? Can be one of form (application/x-www-form-urlencoded), multipart, (multipart/form-data), or json (application/json). For "multipart", list elements can be strings or objects created by
|
user_agent |
A user agent string, prepared by |
Object of class response
from httr.
Other requests and responses:
request_develop()
,
response_process()
## Not run:
req <- gargle::request_build(
method = "GET",
path = "path/to/the/resource",
token = "PRETEND_I_AM_TOKEN"
)
gargle::request_make(req)
## End(Not run)
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.