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

# Get Sync Status Overview

> Check if there are any running sync operations for the current user.

This endpoint provides a simple check to see if the user has any active sync operations
without needing to know specific run IDs.

## Response
Returns a simple status overview:
- **has_running_sync**: Boolean indicating if there are any running syncs
- **running_sync_count**: Number of currently running sync operations
- **latest_running_sync** (optional): Information about the most recent running sync if any exists

## Example Usage
```bash
curl -X GET "http://localhost:8000/api/v1/sync/status" \
  -H "Cookie: auth_token=your-token"
```

## Example Responses

**No running syncs:**
```json
{
  "has_running_sync": false,
  "running_sync_count": 0
}
```

**With running sync:**
```json
{
  "has_running_sync": true,
  "running_sync_count": 1,
  "latest_running_sync": {
    "run_id": "12345678-1234-5678-9012-123456789012",
    "dataset_name": "My Dataset",
    "progress_percentage": 45,
    "created_at": "2025-01-01T00:00:00Z"
  }
}
```



## OpenAPI

````yaml /cognee_openapi_spec.json get /api/v1/sync/status
openapi: 3.1.0
info:
  title: Cognee API
  description: Cognee API with Bearer token and Cookie auth
  version: 1.0.0
servers:
  - url: https://api.cognee.ai
    description: Production server (full functionality)
  - url: http://localhost:8000
    description: Local development server (requires local setup)
security:
  - BearerAuth: []
  - ApiKeyAuth: []
tags:
  - name: activity
    description: ''
  - name: add
    description: Data ingestion endpoints for adding text, files, and structured data.
  - name: auth
    description: >-
      Authentication endpoints for user registration, login, and token
      management.
  - name: checks
    description: ''
  - name: cognify
    description: >-
      Knowledge processing endpoints to transform raw data into knowledge
      graphs.
  - name: configuration
    description: ''
  - name: datasets
    description: Dataset management endpoints for listing, creating, and deleting datasets.
  - name: delete
    description: Data deletion endpoints (deprecated — use datasets endpoints instead).
  - name: forget
    description: ''
  - name: health
    description: ''
  - name: improve
    description: ''
  - name: llm
    description: ''
  - name: memify
    description: ''
  - name: notebooks
    description: ''
  - name: ontologies
    description: ''
  - name: permissions
    description: Permission management for multi-user access control.
  - name: recall
    description: ''
  - name: remember
    description: ''
  - name: responses
    description: Response generation endpoints using the knowledge graph.
  - name: search
    description: Search endpoints for querying the knowledge graph.
  - name: sessions
    description: ''
  - name: settings
    description: Configuration endpoints for managing Cognee settings.
  - name: sync
    description: ''
  - name: update
    description: ''
  - name: users
    description: User management endpoints.
  - name: visualize
    description: Graph visualization endpoints.
paths:
  /api/v1/sync/status:
    get:
      tags:
        - sync
      summary: Get Sync Status Overview
      description: >-
        Check if there are any running sync operations for the current user.


        This endpoint provides a simple check to see if the user has any active
        sync operations

        without needing to know specific run IDs.


        ## Response

        Returns a simple status overview:

        - **has_running_sync**: Boolean indicating if there are any running
        syncs

        - **running_sync_count**: Number of currently running sync operations

        - **latest_running_sync** (optional): Information about the most recent
        running sync if any exists


        ## Example Usage

        ```bash

        curl -X GET "http://localhost:8000/api/v1/sync/status" \
          -H "Cookie: auth_token=your-token"
        ```


        ## Example Responses


        **No running syncs:**

        ```json

        {
          "has_running_sync": false,
          "running_sync_count": 0
        }

        ```


        **With running sync:**

        ```json

        {
          "has_running_sync": true,
          "running_sync_count": 1,
          "latest_running_sync": {
            "run_id": "12345678-1234-5678-9012-123456789012",
            "dataset_name": "My Dataset",
            "progress_percentage": 45,
            "created_at": "2025-01-01T00:00:00Z"
          }
        }

        ```
      operationId: get_sync_status_overview_api_v1_sync_status_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      security:
        - BearerAuth: []
        - ApiKeyAuth: []
components:
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
    ApiKeyAuth:
      type: apiKey
      in: header
      name: X-Api-Key

````