> ## 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 Incremental Cache Update

> Manually triggers an incremental (delta) sync for the specified cache. This syncs only the rows that have changed (inserted, updated, or deleted) since the last successful sync.

Incremental sync is faster than a full refresh because it processes only the delta. This is a one-time manual trigger that runs independently of any configured schedule. If an incremental sync is already running, this call may start a new workflow that will be queued.

Use the Get Cache Status endpoint to monitor the progress of the triggered sync. The `lastIncrementalCacheExecution` 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}/incrementalUpdate
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}/incrementalUpdate:
    post:
      tags:
        - Data -- Cache
      summary: Trigger Incremental Cache Update
      description: >-
        Manually triggers an incremental (delta) sync for the specified cache.
        This syncs only the rows that have changed (inserted, updated, or
        deleted) since the last successful sync.


        Incremental sync is faster than a full refresh because it processes only
        the delta. This is a one-time manual trigger that runs independently of
        any configured schedule. If an incremental sync is already running, this
        call may start a new workflow that will be queued.


        Use the Get Cache Status endpoint to monitor the progress of the
        triggered sync. The `lastIncrementalCacheExecution` field in the status
        response will reflect the new execution.
      operationId: incrementalUpdateCache
      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 sync (UUID format)
          required: true
          schema:
            type: string
          example: 960bd651-7b3c-4511-9a88-18e14ac7742a
      responses:
        '200':
          description: Incremental sync 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

````