Skip to main content
POST
The queue job carries no user context, so the cross-site permission check and the scope resolution MUST happen here before dispatch: without roster:plan-cross-site the pool_units flag is discarded and the run behaves exactly like a single-unit scheduling

Authorizations

Authorization
string
header
required

Bearer-Token, erhalten über den Login-Endpunkt (POST /rest/login).

Path Parameters

roster
string<uuid>
required

The roster ID

Body

application/json
pool_units
boolean
default:false

Response

message
required