Trigger a sync for a connected app on demand (e.g. from automation, after Terraform has connected it). The sync runs asynchronously — the call returns 202 Accepted once the sync is launched; poll GET /apps/{app_id} to follow status.
Requires sync_type (only full_sync is supported today). The app must be connected or in an error state from a prior sync (so callers can retry after failure). Manual/CSV apps are not supported. Only one sync may run at a time: while a sync is in flight the request is rejected with 409 — wait for the running sync to finish, then retry.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Bad request — the request could not be processed. Common causes: missing or malformed credentials, an unknown app_class_id, or an invalid configuration value. See the detail field for the specific reason.
Forbidden — the caller lacks permission to manage apps on this domain.
Not found — no app with this id in your domain.
Conflict — a sync is already running for this app, the app is not in a syncable state, or its first sync is deferred pending admin review (match rules, or a flatfile column mapping) in the Lumos UI.
Unprocessable — sync_type is missing or not a supported value, or the app is a manual/CSV app, which cannot be synced via this endpoint.
Not implemented — this app does not support the requested operation.
Bad gateway — the downstream sync launch failed.