Skip to main content
PATCH
This is the per-employee counterpart to the account-level MVR exemption some clients are temporarily granted — use this when only specific employees need to bypass the gate (e.g. a fund that reliably times out, or while chasing down a rejection with the fund) rather than the whole account. Always fires the employee.mvr_status_changed webhook, whichever direction you set it — see the Webhooks page.

v1 is unaffected

You do not need to adopt the Employees v2 endpoints to use this — MVR, the payment gate, and this override all only ever apply to employees that have a fund identity set through a v2 call at some point. Employees created and managed purely through v1 never have an mvrStatus in the first place, so there is nothing for this endpoint to meaningfully act on for them. Adopt v2 (and MVR) on your own schedule — v1 keeps behaving exactly as it always has either way.

Request Parameters

string
required

Request Body

boolean
required
When true, this employee is exempt from the MVR payment gate: mvrStatus/mvrStatusReason keep updating normally as usual (manual or automatic), but contribution submission is never blocked by them, regardless of what the status is or later becomes. Set false to restore normal gating.
string
Optional free-text note on why this override was set, for audit purposes.

Responses

Response fields

string
boolean
string
Absent when override is false, or when no reason was given.
boolean
integer
string
Last modified on November 10, 2026