#Caching

VibeCode caches responses for /v1/users (60 s) and /v1/statuses (5 min) when using an APP-mode API key. This dramatically speeds up dashboards that fetch these endpoints on every load.

#How to opt out per-request

Send Cache-Control: no-cache header. The request bypasses the cache and hits Bitrix24 directly.

Terminal 
curl -H "X-Api-Key: vibe_api_..." -H "Cache-Control: no-cache" https://vibecode.bitrix24.tech/v1/users

#Response headers

  • X-Cache: HIT — served from cache
  • X-Cache: MISS — fetched from Bitrix24, now cached
  • X-Cache: COALESCED — joined an in-flight fetch started by another request
  • X-Cache: BYPASS — cache was skipped (OAuth mode, no-cache header, or cache disabled platform-wide)

#What about OAuth-app mode?

OAuth-app keys bypass the cache — different users may see different data based on their portal permissions.

#Freshness after writes

Writes via the platform (POST /v1/users, PATCH /v1/users/:id, etc.) invalidate the cache immediately. Writes made directly in the Bitrix24 UI are not seen — expect up to TTL (60 s for users, 5 min for statuses) of staleness.