Features/REST API

Dynamic request properties

Define properties on a request and change them per element in the builder to adjust the URL, params or body.

Properties are named inputs for a request, with default values. They show up as inputs in the builder Source panel, so each element bound to the request can pass its own values. Inside the request you reference them in the URL, params, headers or body, so one request definition can serve many pages, for example fetching a record by slug.

How it works

  • Property keys are lowercased, spaces become dots, and only a-z 0-9. _ are kept; rows with empty key or value are dropped.
  • In the builder each property is an input field with the default value.
  • Values are passed as $properties during URL/param/header/body processing.
  • Different property values give different cache keys.

When to use it

  • Fetch a single item by slug on a dynamic page
  • Pass a category or page number to the API

Limitations

  • Property values must be scalars (non-scalar values are dropped by the run action)

Availability

  • Works in Designer.
  • Included in every plan.

How to use it.

  1. Open the request > Advanced > Properties
  2. Add a key and default value
  3. Use it in the URL, params or body
  4. In the builder override it in the Source panel

Questions.

Can a property be empty by default?

Related features.

No card needed

Build it today.Pay when it goes live.

Every feature is unmetered while you build. Checkout opens the first time you publish.