Whether to allow this request to pull from cache if available
Whether requests to the same route should be allowed to be stacked, see Config.allowStackingByDefault
Stacked requests only use a single API request and return the EXACT same object as all other requests in the stack.
Keeping this enabled can cause errors if requested data is mutated in downstream code
The API key to use in this request
The key has to be registered in the config.
If this is not given, the registered key with the most free requests will be selected.
The amount of time the request should be cached for, overwrites the defaults specified in the config
Whether to ignore version errors
You can use this to resolve temporary conflicts while the library awaits being updated. Otherwise it should stay enabled.
Whether errors or profiles not being found should be
filtered out and throw errors/return null
Whether this request should be put to the front of the queue, executing before any non-priority requests are handled
The amount of times to retry the request on error
The API route to request
The expected version or request.version property, responses with another version will throw an error
The amount of milliseconds a until the request should be rejected

Generated using TypeDoc
The options for a raw API request