Skip to main content
POST
Move a member to another rule

Autorisierungen

X-API-KEY
string
header
erforderlich

Pfadparameter

member_id
string<uuid>
erforderlich
Pattern: ^([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})$

Body

application/json
current_assignment_id
integer
erforderlich

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

Erforderlicher Bereich: -9007199254740991 <= x <= 9007199254740991
rule_id
string<uuid>
erforderlich

The rule to move the member to.

Pattern: ^([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})$
allowance_type_id
string<uuid>
erforderlich
Pattern: ^([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})$
valid_from
string
erforderlich

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

Pattern: ^\d{4}-\d{2}-\d{2}$
reason
string
erforderlich

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

Required string length: 3 - 500
valid_until
string | null

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.

Pattern: ^\d{4}-\d{2}-\d{2}$

Antwort

Successful response

success
boolean
erforderlich