Skip to main content


The ZuploRequest object is the main parameter passed to both RequestHandlers and Policies. It represents the incoming request.

ZuploRequest inherits from the web standard Request class used with fetch - you can read more about this on MDN including an explanation of how all of its properties and methods work:

In addition to the standard properties, the following are added for convenience.


  • params - if you use tokens in your route’s URL, we automatically parse them into properties on the params property of your request. For example, imagine a route with path /products/:productId/vendors/:vendorId. A match on this would yield values as follows:
const productId = request.params.productId;
const vendorId = request.params.vendorId;
  • user - an optional object identifying a ‘user’. If undefined this typically means the request is anonymous. If present, the user object will have a sub property that is a unique identifier for that user. There is also an optional data property that is of any type that typically contains other information about the user. When using JWT tokens you’ll usually find all the claims here.
  • query - a dictionary of query-string values. For example, a URL with a query string like would present as follows:
const foo =;


It can be useful to create a new ZuploRequest inside a policy (see policies) to forward to the next policy or handler in the chain. You can create a completely fresh ZuploRequest as follows:

const newCoreRequest = new Request("", {
method: "POST",
headers: {
"content-type": "application/json",
body: "test",

const newZuploRequest = new ZuploRequest(newCoreRequest);