---
title: "Get structural sync status"
method: GET
path: "/org/kb/sync-status"
tags: ["Knowledge Base"]
---

# Get structural sync status

`GET /org/kb/sync-status`

## Request

- Base URL: `https://apiv2.senso.ai/api/v1`
- URL: `https://apiv2.senso.ai/api/v1/org/kb/sync-status`
- Auth: API key in header `X-API-Key`

Reports whether queued structural changes — moves and deletes — are still propagating. Both go through a queue before taking full effect, and a move changes who can reach a document: access is derived from the folder a node sits in, so after moving a document into a folder, the people who can read that folder cannot query it until this reports done. Deletes settle the same way.

This is not an ingestion signal, and it is not scoped to one document. To learn whether a newly ingested document is queryable, poll that document's `GET /org/kb/nodes/{id}` and read `content.processing_status`.

## Response `200`

The sync status.

- KBSyncStatusResponse
  - `syncing` boolean, required: True while queued move and delete operations are still propagating across the organization's knowledge base. Not an ingestion signal — a document's own `content.processing_status` reports that.

## Other responses

- `401`: Missing or invalid credentials — supply a valid org API key in the `X-API-Key` header.
- `403`: The API key is authenticated but not permitted to access this resource.

---

[API](https://skmtc.dev/senso/apis/senso-org-api.md) - [All operations](https://skmtc.dev/senso/apis/senso-org-api/llms.txt) - [OpenAPI document](https://skmtc.dev/senso/apis/senso-org-api/revisions/d789b4fcbe84?raw)