> ## Documentation Index
> Fetch the complete documentation index at: https://docs.peaka.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Trigger Full Refresh Cache Update

> 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.

<span style={{display: "flex", gap: "10px", flexDirection: "row", alignItems: "center"}}>
  <img src="https://cdn.peaka.com/badges/partner-api-key-badge.png" />

  <img src="https://cdn.peaka.com/badges/project-api-key-badge.png" />
</span>


## OpenAPI

````yaml post /data/projects/{projectId}/cache/{cacheId}/fullRefreshUpdate
openapi: 3.0.1
info:
  title: Peaka Gateway API
  description: Peaka Gateway API Documentation
  version: '1.0'
servers:
  - url: https://partner.peaka.studio/api/v1
    description: Default Server URL (US Zone)
  - url: https://partner.eu.peaka.studio/api/v1
    description: EU Zone
security:
  - bearerAuth: []
paths:
  /data/projects/{projectId}/cache/{cacheId}/fullRefreshUpdate:
    post:
      tags:
        - Data -- Cache
      summary: Trigger Full Refresh Cache Update
      description: >-
        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.
      operationId: fullRefreshCache
      parameters:
        - name: projectId
          in: path
          description: The unique identifier of the project that owns the cache
          required: true
          schema:
            type: string
          example: mtKDhe1U
        - name: cacheId
          in: path
          description: The unique identifier of the cache to fully refresh (UUID format)
          required: true
          schema:
            type: string
          example: 960bd651-7b3c-4511-9a88-18e14ac7742a
      responses:
        '200':
          description: Full refresh triggered successfully.
          content:
            '*/*':
              schema:
                type: object
                additionalProperties:
                  type: object
        '404':
          description: Cache not found for the given cacheId.
          content:
            '*/*':
              schema:
                type: object
                additionalProperties:
                  type: object
components:
  securitySchemes:
    bearerAuth:
      type: http
      description: >-
        Use the Authorization header with the value 'Bearer <apiKey>' to
        authenticate. Partner API Keys have full access; Project API Keys are
        limited to their project scope. Learn more:
        https://docs.peaka.com/api-reference/authentication
      scheme: bearer
      bearerFormat: Api Key

````