Skip to main content
POST
Why it’s useful: Use it to make sure the member you are onboarding can receive superannuation contributions with the details they gave you. Funds can take up to 24 hours to respond.
Employer, fund, and member details are resolved server-side from the employee’s stored record — you only need to supply the employeeId. Use this endpoint to:
  • Manually (re-)run verification for a v1 employee without otherwise updating their record
  • Retry a REJECTED or NOT_SUPPORTED employee after confirming their details are correct
  • Force a check ahead of submitting a contribution for a client with more than one onboarded employer (via employerId)
Note: use GET /v2/mvr/:transactionId (with the transactionId returned here) to poll the outcome, or watch for the employee.mvr_status_changed webhook.

Request Body

string
required
The employeeId of the member to run a Member Verification Request for. Employer, fund, and member details are resolved server-side from this employee’s stored record.
string
Optional explicit employerId to use instead of auto-picking the eligible employer for the client. Use when you already know which employer this employee’s contribution was actually sent through, since a client with more than one onboarded-and-synced employer has no reliable way to auto-pick the right one.

Responses

Response fields

string
SuperChoice transaction ID for this MVR submission. Use it to poll GET /v2/mvr/:transactionId for the outcome.
string
Always PENDING immediately after a successful submission — the employee’s mvrStatus is set to this at the same time.
boolean
integer
string
integer
Last modified on November 10, 2026