Set a member's default and hidden allowance types
Sets which allowance type is preselected for a member (default) and whether a type is hidden from them (disabled). Until now this was only reachable through the set_as_default / disabled fields of the deprecated PUT /members//allowance//, so an integration that stopped calling that endpoint lost the ability to set the default at all. One invariant is enforced for you: a member always has exactly one default type. Setting default: true therefore demotes the previous default, and hiding the current default promotes the oldest remaining visible type. Known limit: if the member has no OTHER visible type, hiding the addressed one is accepted and leaves that type both default and hidden, so the member sees no allowance at all — check allowance_type_configurations in GET /members/ before hiding a type. A single call can rewrite sibling rows, so read the member back via GET /members/ if you need the resulting allowance_type_configurations. Both fields are required: the request states the complete desired state for this one allowance type, it is not a partial update. That is deliberate — the two flags are resolved together, so a merge against a separately read row could resolve against a state that no longer holds. GET /members/ already returns both current values under allowance_type_configurations. To set this when creating a member, use the defaultAllowances array of POST /members instead.
Authorizations
Path Parameters
^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$Body
Response
Successful response