Skip to main content
Some brokers run elections and payroll deductions themselves and have Prescience set up member accounts. Prescience sets this per partner (benefitsAdmin: prescience, the default, or partner).

Submit elections

After the group’s enrollment exists, send each employee’s final election. This is also the MCP tool submit_elections.
POST /groups/{groupId}/elections
  • Identify each employee by memberId or externalId.
  • election is enrolled or waived. effectiveDate (YYYY-MM-DD) is required for an enrolled election; waiverReason is optional on a waiver.
  • tier (employeeOnly, employeeSpouse, employeeChildren, family) must match the covered dependents (relationship: spouse, domestic_partner, child or other; dob and name optional).
  • Up to 10,000 elections per request. Send an Idempotency-Key to make a retry safe.
  • Valid rows are applied; invalid rows come back in errors by index. The response is 400 invalid_request when no row is valid, and 409 conflict until the group’s enrollment exists.
Response (200)
Prescience marks the elections on the group’s census, records each coverage effective date and emails each enrolled member a login (invited counts them). Test-mode groups never send email (invitesSuppressed: "test-mode"). The endpoint is also the MCP tool submit_elections.

Payroll deductions

When benefitsAdmin is partner, Prescience sends a deductions.changed webhook after elections are applied (deductionsWebhook is true), with each submitted member’s coverage and deduction exactly as GET /groups/{groupId}/members shows them (see Payroll deductions):