> ## Documentation Index > Fetch the complete documentation index at: https://infisical.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Update > Update the specified Supabase Sync. ## OpenAPI ````yaml PATCH /api/v1/secret-syncs/supabase/{syncId} openapi: 3.0.3 info: title: Infisical API description: List of all available APIs that can be consumed version: 0.0.1 servers: - url: https://us.infisical.com description: Production server (US) - url: https://eu.infisical.com description: Production server (EU) - url: http://localhost:8080 description: Local server security: [] paths: /api/v1/secret-syncs/supabase/{syncId}: patch: tags: - Secret Syncs description: Update the specified Supabase Sync. operationId: updateSupabaseSecretSync parameters: - schema: type: string format: uuid in: path name: syncId required: true description: The ID of the Supabase Sync to be updated. requestBody: required: true content: application/json: schema: type: object properties: name: type: string minLength: 1 maxLength: 256 description: >- The updated name of the Supabase Sync. Must be slug-friendly. connectionId: type: string format: uuid description: >- The updated ID of the Supabase Connection to use for syncing. description: type: string maxLength: 256 nullable: true description: The updated description of the Supabase Sync. environment: type: string minLength: 1 maxLength: 64 description: >- The updated slug of the project environment to sync secrets from. secretPath: type: string minLength: 1 description: The updated folder path to sync secrets from. isAutoSyncEnabled: type: boolean description: >- Whether secrets should be automatically synced when changes occur at the source location or not. syncOptions: type: object properties: initialSyncBehavior: type: string enum: - overwrite-destination description: >- Specify how Infisical should resolve the initial sync to the Supabase destination. keySchema: type: string description: >- Specify the format to use for structuring secret keys in the Supabase destination. disableSecretDeletion: type: boolean description: >- Enable this flag to prevent removal of secrets from the Supabase destination when syncing. required: - initialSyncBehavior additionalProperties: false description: Optional parameters to modify how secrets are synced. destinationConfig: type: object properties: projectId: type: string minLength: 1 maxLength: 255 projectName: type: string minLength: 1 maxLength: 255 required: - projectId - projectName additionalProperties: false additionalProperties: false responses: '200': description: Default Response content: application/json: schema: type: object properties: secretSync: type: object properties: id: type: string format: uuid name: type: string description: type: string nullable: true isAutoSyncEnabled: type: boolean default: true version: type: number default: 1 projectId: type: string folderId: type: string format: uuid nullable: true connectionId: type: string format: uuid createdAt: type: string format: date-time updatedAt: type: string format: date-time syncStatus: type: string nullable: true lastSyncJobId: type: string nullable: true lastSyncMessage: type: string nullable: true lastSyncedAt: type: string format: date-time nullable: true importStatus: type: string nullable: true lastImportJobId: type: string nullable: true lastImportMessage: type: string nullable: true lastImportedAt: type: string format: date-time nullable: true removeStatus: type: string nullable: true lastRemoveJobId: type: string nullable: true lastRemoveMessage: type: string nullable: true lastRemovedAt: type: string format: date-time nullable: true syncOptions: type: object properties: initialSyncBehavior: type: string enum: - overwrite-destination description: >- Specify how Infisical should resolve the initial sync to the Supabase destination. keySchema: type: string description: >- Specify the format to use for structuring secret keys in the Supabase destination. disableSecretDeletion: type: boolean description: >- Enable this flag to prevent removal of secrets from the Supabase destination when syncing. required: - initialSyncBehavior additionalProperties: false description: Optional parameters to modify how secrets are synced. connection: type: object properties: app: type: string enum: - supabase name: type: string id: type: string format: uuid required: - app - name - id additionalProperties: false environment: type: object properties: slug: type: string name: type: string id: type: string format: uuid required: - slug - name - id additionalProperties: false nullable: true folder: type: object properties: id: type: string path: type: string required: - id - path additionalProperties: false nullable: true destination: type: string enum: - supabase destinationConfig: type: object properties: projectId: type: string minLength: 1 maxLength: 255 projectName: type: string minLength: 1 maxLength: 255 required: - projectId - projectName additionalProperties: false required: - id - name - projectId - connectionId - createdAt - updatedAt - syncOptions - connection - environment - folder - destination - destinationConfig additionalProperties: false title: Supabase required: - secretSync additionalProperties: false '400': description: Default Response content: application/json: schema: type: object properties: reqId: type: string statusCode: type: number enum: - 400 message: type: string error: type: string details: {} required: - reqId - statusCode - message - error additionalProperties: false '401': description: Default Response content: application/json: schema: type: object properties: reqId: type: string statusCode: type: number enum: - 401 message: type: string error: type: string required: - reqId - statusCode - message - error additionalProperties: false '403': description: Default Response content: application/json: schema: type: object properties: reqId: type: string statusCode: type: number enum: - 403 message: type: string details: {} error: type: string required: - reqId - statusCode - message - error additionalProperties: false '404': description: Default Response content: application/json: schema: type: object properties: reqId: type: string statusCode: type: number enum: - 404 message: type: string error: type: string required: - reqId - statusCode - message - error additionalProperties: false '422': description: Default Response content: application/json: schema: type: object properties: reqId: type: string statusCode: type: number enum: - 422 message: {} error: type: string required: - reqId - statusCode - error additionalProperties: false '500': description: Default Response content: application/json: schema: type: object properties: reqId: type: string statusCode: type: number enum: - 500 message: type: string error: type: string required: - reqId - statusCode - message - error additionalProperties: false ````