Turn on session cookie data storage for your API — api_session

If you need to keep data between requests, but don't want to store it server-side you can instead pass it back and forth as an encrypted session cookie. This function sets it up on your api and after it's use you can now access and set session data in the request and response $session field. Be aware that session data is send back and forth with all requests and should thus be kept minimal to avoid congestion on your server.

Usage

api_session_cookie(
  api,
  key,
  name = "reqres",
  expires = NULL,
  max_age = NULL,
  path = NULL,
  secure = NULL,
  same_site = NULL
)

Arguments

api: A plumber2 api object to add the session cookie setup to
key: A 32-bit secret key as a hex encoded string or a raw vector to use for encrypting the session cookie. A valid key can be generated using reqres::random_key(). NEVER STORE THE KEY IN PLAIN TEXT. Optimalle use the keyring package to store it
name: The name of the cookie
expires: A POSIXct object given the expiration time of the cookie
max_age: The number of seconds to elapse before the cookie expires
path: The URL path this cookie is related to
secure: Should the cookie only be send over https
same_site: Either "Lax", "Strict", or "None" indicating how the cookie can be send during cross-site requests. If this is set to "None" then secure must also be set to TRUE

Value

These functions return the api object allowing for easy chaining with the pipe