Manually triggers a full refresh (resync) for the specified cache. This drops all existing cached data and rebuilds the cache from scratch by re-reading the entire source table.
Full refresh is more expensive than incremental sync but ensures complete data consistency. It is useful when the source data has drifted or when schema changes have occurred. This is a one-time manual trigger that runs independently of any configured schedule.
Use the Get Cache Status endpoint to monitor the progress of the triggered refresh. The lastFullRefreshCacheExecution field in the status response will reflect the new execution.


Use the Authorization header with the value 'Bearer
The unique identifier of the project that owns the cache
The unique identifier of the cache to fully refresh (UUID format)
Full refresh triggered successfully.