Updates an account in your own part of the hierarchy. Every field is optional; a request with an empty body succeeds and changes nothing.
meta is stored whole. The object you send replaces the stored one rather than merging into it, so an update carrying only meta.publish clears meta.join, meta.promote and meta.hide_from_new_applicants. Send every key you want to keep.
This endpoint answers in one of two shapes, both with a 200. Normally it returns the updated account, the same shape as reading it. But a request that carries a permissions object differing from the one already stored is handed to a background job instead, and the response is {"queue": "<token>"} - nothing has been saved by the time it returns, the rest of the fields in that request are applied in the background too, and the token is not something you can poll. Read the account back to confirm the outcome. permissions describes what features the account itself may use and is not something an ordinary caller can change; sending it still switches the response shape, and it is then ignored.
Fields beyond the ones below are accepted from callers with elevated access. The account's own configured attributes are accepted as custom_* fields.
Display name of the sub-account, up to 255 characters. This is what people see in the account switcher and in anything branded with the account name.
Optional conditions narrowing which people may see or join this sub-account. Structure is not part of the contract and is not validated - build the rules in the admin console and send back what a read returns. Send an empty array to clear them.
Position of the sub-account in lists that show a group of them together. Lower sorts first; accounts sharing a value fall back to name order.
When the sub-account becomes active, as YYYY-MM-DD HH:MM:SS. Must be within 25 years either side of now. Leave null for an account that is active immediately.
When the sub-account stops being active, as YYYY-MM-DD HH:MM:SS. Must be later than start_timestamp and within 25 years of now. Leave null for no end.
Whether the account is archived. An archived account keeps its data but is hidden from the places an active one appears. Update only.
- Mock serverhttps://developer.rosterfy.com/_mock/api-docs/openapi/api/v2/account/{id}
- Your Rosterfy accounthttps://example.rosterfy.com/api/v2/account/{id}
curl -i -X PUT \
'https://developer.rosterfy.com/_mock/api-docs/openapi/api/v2/account/{id}' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-H 'Rosterfy-Platform: admin' \
-d '{
"name": "Example Organisation",
"meta": {
"publish": true
},
"visibility_rules": [],
"sort_order": 0,
"start_timestamp": null,
"end_timestamp": null,
"is_archived": 0,
"custom_*": null
}'{ "queue": "mTsVQ1NCLS3vg7WwP5kG1Vbt" }