Hey Daniele,
First of all, thanks for Bricksforge — the External API feature is super useful. Caching already works great: Bricksforge stores responses via the WordPress Transients API (plus an in‑memory cache per request), so results are shared across visitors during the cache lifetime.
What I still miss: a simple safety net to make sure an API quota can never be exceeded.
Request
- Add a Daily request limit field per External API item (e.g. 950/day).
- When the cap is reached, stop sending upstream requests and keep serving the last cached result (or display a small fallback message).
- (Nice to have) Show a tiny counter in the UI (e.g. “Today: 743 / 950”).
Why this helps
- Removes the need to manually compute cache duration as a workaround (86400 / quota).
- Protects against traffic spikes & bots across multiple pages.
- Gives peace of mind for small clients where cost control is essential.
(Optional note) If feasible, it would also be helpful if the cache key could include the normalized URL + query parameters, so different parameter combinations of the same item don’t accidentally share one cache entry. This is not critical for the daily limit, but it would make caching even more predictable.
Thanks a lot for considering this — happy to test or provide more details if needed!