Send an authenticated API request on the user's behalf and return an
httr2 response. Pass the token from login and the API URL, then read the
response with httr2::resp_body_json() or another httr2 response helper.
Usage
perform_resource_req(
token,
url,
method = "GET",
headers = NULL,
query = NULL,
follow_redirect = FALSE,
check_url = TRUE,
client = NULL,
token_type = NULL,
dpop_nonce = NULL,
idempotent = NULL,
resource_hosts = NULL,
oauth_client = NULL
)Arguments
- token
Either an OAuthToken object or a raw access token string.
- url
The absolute API URL, or a prepared
httr2::request()object. The URL must be at most 8192 bytes before and after addingquery. The helper adds current authentication and defaults to a prepared request, then applies explicitmethod,headers,queryand redirect overrides. See Prepared requests for customization restrictions.- method
Optional HTTP method (character). Defaults to "GET". When the effective token type is
DPoP, this must be the final request method because the proof is signed against it.TRACEand the nonstandardTRACKmethod are rejected because authenticated requests could be reflected by the server and disclose credentials.- headers
Optional named list or named character vector of extra headers to set on the request. Header names are case-insensitive. Names must be unique HTTP field-name tokens, and values must not contain prohibited control characters. DPoP requests reject
Hostoverrides. This function manages theAuthorizationandDPoPheaders and ignores user-supplied replacements.- query
Optional named list of query parameters to append to the URL.
- follow_redirect
Logical or
NULL.FALSE(the default) disables HTTP redirects even whenshinyOAuth.allow_redirectis enabled.NULLinherits that global option (disabled by default).TRUEenables redirects. DPoP requests reject enabled redirects because each target needs a new proof.- check_url
Logical. If
TRUE(the default), validatesurlagainstis_ok_host()before attaching the access token. This rejects relative URLs, plain HTTP to non-loopback hosts, and whenoptions(shinyOAuth.allowed_hosts)is set, hosts outside the allowlist. Without an allowlist this performs HTTPS and URL-syntax validation only (with the configured non-HTTPS exceptions); any HTTPS host is accepted.FALSEskips this policy check; URL length and resource-host restrictions still apply.- client
Optional OAuthClient; required for DPoP or mTLS-bound tokens so the request can use the matching signing key or certificate and check any token-binding information.
- token_type
Optional override for the access token type when
tokenis supplied as a raw string. Supported values areBearerandDPoP. Invalid or multi-valued inputs are rejected. When omitted, shinyOAuth preservesOAuthToken@token_type, and may inferDPoPfrom explicitOAuthToken@cnf[["jkt"]]metadata. Raw access-token strings default toBearerunless you passtoken_type = "DPoP"explicitly.- dpop_nonce
Optional DPoP nonce to embed in the proof for this request. This is primarily useful after a resource server challenges with
DPoP-Nonce.- idempotent
Whether ordinary network/HTTP failures may be retried safely.
NULL(default) infers this from the final HTTP method: GET, HEAD, OPTIONS, PUT, and DELETE permit retries. Set it explicitly if your API has different guarantees. One DPoP nonce challenge retry is allowed independently of this setting.- resource_hosts
Optional non-empty character vector of trusted resource host patterns, using
is_ok_host()matching rules. This call-scoped allowlist adds to the global policy and is enforced even ifcheck_urlisFALSE. It constrains the initial URL, not redirect destinations or resolved IPs.NULLadds no resource-specific policy.- oauth_client
Compatibility alias for
client. Supply only one spelling.
Value
An httr2 response object.
Details
The package applies its URL policy, timeouts and redirect defaults. It supports
Bearer authentication and tokens tied to a key (DPoP) or certificate (mTLS).
For DPoP or mTLS, client supplies the matching key or certificate.
The helper applies shinyOAuth.max_body_bytes to response bodies, including
gzip decompression. Use it for both URL strings and prepared httr2 requests.
Prepared requests
Use httr2::req_method() and body helpers to prepare a request, then let
shinyOAuth manage authentication and retries. Existing httr2 authentication,
caching and retry policies, and curl authentication, method-changing or
request_target options are rejected. HEAD requests cannot have bodies,
because httr2 may send those as POST. Authenticated response caching is
unsupported. Configure retries with idempotent and shinyOAuth.retry_*.
Examples
# Make request using OAuthToken object
# (code is not run because it requires a real token from user interaction)
if (interactive()) {
# Inside reactive server code, after login has succeeded:
token <- auth[["token"]]
# Build and send in one step.
response <- perform_resource_req(
token,
"https://api.example.com/resource",
query = list(limit = 5)
)
# Prepare a request before sending it.
request <- resource_req(
token,
"https://api.example.com/resource",
query = list(limit = 5)
)
# Sending the prepared request applies the same response-size limits.
response <- perform_resource_req(token, request)
# Or start from your own httr2 request and still let shinyOAuth perform it
# so response limits and DPoP nonce retries remain available.
custom_request <- httr2::request("https://api.example.com/resource") |>
httr2::req_headers(Accept = "application/json") |>
httr2::req_url_query(limit = 5)
response <- perform_resource_req(token, custom_request)
# resource_hosts restricts this dynamic URL to api.example.com.
response <- perform_resource_req(
token,
input[["resource_url"]],
resource_hosts = "api.example.com",
follow_redirect = FALSE
)
}