---
title: "Trigger GitOps synchronization"
method: POST
path: "/admin/gitops/sync"
tags: ["GitOps", "Admin"]
---

# Trigger GitOps synchronization

`POST /admin/gitops/sync`

**Experimental.** Requests an immediate synchronization of the GitOps storage. This resets the poll timer so the next scheduler cycle will poll the Git repository without waiting for the configured poll period.

The synchronization happens asynchronously — this endpoint returns immediately and the actual sync occurs on the next scheduler cycle.

This endpoint is only available when GitOps storage is enabled (`apicurio.storage.kind=gitops`). Returns HTTP 409 (Conflict) if a different storage backend is active.

This operation can fail for the following reasons:

* GitOps storage is not enabled (HTTP error `409`)
* A server error occurred (HTTP error `500`)

## Response `204`

Synchronization has been requested. The sync will happen asynchronously on the next scheduler cycle.

## Other responses

- `401` — Common response for all operations that can return a `401` error indicating authentication is required.
- `403` — Common response for all operations that can return a `403` error indicating the user is authenticated but not authorized.
- `409` — Common response used when an input conflicts with existing data.
- `500` — Common response for all operations that can fail with an unexpected server error.

---

[API](https://skmtc.net/apicurio/apis/apicurio-registry-api-v3.md) · [All operations](https://skmtc.net/apicurio/apis/apicurio-registry-api-v3/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/apicurio/apicurio-registry-api-v3/revisions/c39cb56d7dbc/schema)