Switch a member to manual allowance management
Takes the member off automatic accrual for this allowance type from valid_from on. Nothing accrues afterwards, and the balance is whatever you set through adjustments. Pass the member’s active assignment as current_assignment_id and it is ended on valid_from in the same transaction; without it, an assignment overlapping valid_from makes the call fail.
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)$Body
^([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)$First day the member is managed manually (inclusive), in YYYY-MM-DD format.
^\d{4}-\d{2}-\d{2}$Why the member is managed manually — stored in the rule audit log.
3 - 500Last day of manual management (inclusive), in YYYY-MM-DD format, or null for open-ended.
^\d{4}-\d{2}-\d{2}$The assignment that is active today, from GET /members/{member_id}/rule-assignments. Send null when the member has none.
-9007199254740991 <= x <= 9007199254740991Response
Successful response