---
title: "Trigger Scim Sync"
method: POST
path: "/v1/admin/scim/sync"
tags: ["beta.admin.scim"]
---

# Trigger Scim Sync

`POST /v1/admin/scim/sync`

Trigger an on-demand SCIM synchronization for the Organization.

Requires SAML authentication to be enabled and the Organization to be in SCIM
user provisioning mode. A dry run previews every change without applying it;
a real run applies the categories selected in `sync_config`. Only one run may
be active at a time — a conflicting request returns the already-active run.

## Request body

- AdminScimSyncTriggerIN
  - `dry_run` boolean — Preview all synchronization changes without applying them.
  - `sync_config` AdminScimSyncConfig
    - `delete_missing_groups` boolean — Delete Organization groups that are absent from the SCIM provider.
    - `deprovision_users` boolean — Remove Organization users that are inactive or absent from the SCIM provider.
    - `sync_users` boolean, required — Add users found in the SCIM provider to the Organization.
    - `sync_groups` boolean, required — Synchronize group metadata from the SCIM provider.
    - `sync_memberships` boolean, required — Synchronize additions and removals of users in SCIM groups.

## Response `202`

Accepted

- AdminScimSyncTriggerOUT
  - `run_id` string, uuid, required — Unique identifier of the created SCIM synchronization run.

## Other responses

- `409` — Conflict

---

[API](https://skmtc.net/mistral/apis/mistral-ai-api.md) · [All operations](https://skmtc.net/mistral/apis/mistral-ai-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/mistral/mistral-ai-api/revisions/61436a496404/schema)