Verzeichnis-Synchronisation konfigurieren
Idempotent upsert — always 200, also on the first write.
Bearer-Token, erhalten über den Login-Endpunkt (POST /rest/login).
Ort: header
Pfadparameter
Request-Body
application/json
TypeScript-Definitionen
TypeScript-Typ für request body.
Validation of one provider's provisioning setup.
The cross-field rules all guard the same thing: switching the sync on without everything it needs would produce an hourly failing run rather than an error the administrator sees while configuring.
Response-Body
application/json
application/json
application/json
curl -X PUT "https://example.com/sso/sync/string" \ -H "Content-Type: application/json" \ -d '{}'{ "data": { "id": "string", "provider": "string", "configured": true, "enabled": true, "auto_commit": true, "group_id": "string", "admin_email": "string", "default_schedule_model_id": "string", "default_holiday_calendar_id": "string", "runnable": true, "requires_admin_email": true, "credentials_configured": true, "synced_at": "string", "last_error": "string", "last_run": null, "updated_at": "string" }}Verzeichnis-Synchronisation abrufen GET
Every supported provider, configured or not — an unconfigured one comes back as a disabled placeholder so the admin screen binds against one list and does not have to know the provider catalogue.
Verzeichnis-Synchronisation simulieren POST
Reads the directory and returns the full action list. Writes nothing but the run record. Synchronous: a group is a bounded set and the screen needs the answer to be actionable.