Allowance Management

Move a member to another rule

Changed on

Ends the member's current assignment on valid_from and starts the new rule on the same day, in one transaction. Prefer this over deleting and recreating assignments: it leaves neither a gap nor an overlap, and records the move as a single audit entry. A valid_until is only accepted on the day before the next assignment starts or on the member's last employment day, so send null when nothing follows. Gaps or overlaps that predate this rule are tolerated, but the move may not widen them.

post/members/{member_id}/rule-change

Request

  • Base URL
    https://api.absentify.com/api/v1
  • URL
    https://api.absentify.com/api/v1/members/{member_id}/rule-change
  • Auth
    API key in header X-API-KEY

Path parameters

member_idstring uuid required

Request body

current_assignment_idinteger required

The assignment being replaced, from GET /members/{member_id}/rule-assignments.

rule_idstring uuid required

The rule to move the member to.

allowance_type_idstring uuid required
valid_fromstring required

First day the new rule applies (inclusive), in YYYY-MM-DD format. Must be after the current assignment's start date.

valid_untilstring nullable

Last day the new rule applies (inclusive), in YYYY-MM-DD format, or null for open-ended. To cover the member through 2026-08-31, send 2026-08-31.

reasonstring required

Why the member is being moved — stored in the rule audit log.

Response

Successful response

successboolean required

Changes

    • warning

      changed the pattern of the path request parameter member_id from ^([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)$ to ^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$

    • warning

      changed the pattern of the request property from ^([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)$ to ^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$

    • warning

      changed the pattern of the request property from ^([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)$ to ^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})$

    • info

      endpoint added