- Add people to a functional area
Adds a list of people to the functional area named in the URL, all with the same membership status. The work is queued rather than done while you wait, so a 200 means the request was accepted, not that anyone has been added yet.
Send this request as form-encoded parameters, not as a JSON body. A JSON body is not read for selected, and the request is reported as not found.
People who cannot be added are skipped rather than reported: IDs that do not resolve, people in another account, and anyone already in the group. The response does not say how many were added, and the queue value it returns is a correlation reference that no endpoint resolves - there is nothing to poll. Confirm the outcome by listing the group's members.
The IDs of the people to add to the group. Required - a request without it is not found rather than rejected as invalid. IDs that do not resolve, belong to another account, or are already in the group are skipped without being reported.
The membership status each person is added with: pending, accepted or rejected. Required, and any other value is rejected.
Required, and conventionally selected. This endpoint always adds exactly the people listed in selected, so the value sent does not change what happens - but the request is rejected if the field is missing. Note the camelCase name, which is deliberate here and differs from the snake_case used elsewhere.
- Mock serverhttps://developer.rosterfy.com/_mock/api-docs/openapi/api/v2/headcount/functionalarea/{functionalarea_id}/user/mass-create
- Your Rosterfy accounthttps://example.rosterfy.com/api/v2/headcount/functionalarea/{functionalarea_id}/user/mass-create
curl -i -X POST \
'https://developer.rosterfy.com/_mock/api-docs/openapi/api/v2/headcount/functionalarea/{functionalarea_id}/user/mass-create' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-H 'Rosterfy-Platform: admin' \
-d '{
"selected": [],
"status": null,
"applyTo": null
}'