Features/REST API

REST API caching

Cache REST API responses for 1 minute up to 1 month so pages load fast and the external API is called less.

Each REST request has a Cache setting. When set, the response is stored in Redis and served from there until the duration ends. The cache key includes the request id, its last update time, the properties and the final URL, so changing the request or passing different properties produces a fresh call.

How it works

  • Options in the UI: None, 1 Minute, 5 Minutes, 15 Minutes, 30 Minutes, 1 Hour, 6 Hours, 12 Hours, 1 Day, 7 Days, 15 Days, 1 Month (values in seconds 0 to 2592000).
  • Server clamps the value to 0..2592000 seconds (30 days).
  • Only successful responses are used for source/variable output (execute(..., successOnly=true)).
  • The UI says 'Source must be enabled'; caching applies to source and variable execution.
  • Editing the request changes 'updated', which invalidates the old cache entry.
  • Airtable has its own cache duration setting (None up to 7 Days). Strapi sources are not cached. Shopify products are live calls (recache only stores a product list for the admin).

When to use it

  • Cache a slow third-party API for an hour
  • Keep API usage under a provider's rate limit

Limitations

  • Maximum 30 days
  • No manual 'clear cache' button for a single request; editing the request invalidates it
  • The 'Run API' button in the editor always calls the API (no cache)

Availability

  • Works in Designer.
  • Included in every plan.
  • Limits: 0 to 2592000 seconds

How to use it.

  1. Open the request
  2. Enable Source
  3. Pick a Cache duration

Questions.

How do I refresh cached data early?

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.