Skip to main content
Bolto can keep employers inside its benefits UI while Prescience handles census confirmation, preliminary pricing, spouse/dependent collection, and onboarding.

Flow

  1. Bolto creates the employer group and syncs census from Check.
  2. Bolto mints an embed session server-side.
  3. Bolto renders the returned iframe URL in its marketplace UI.
  4. The employer reviews the roster, excludes employees if needed, previews a preliminary estimate, and clicks Finalize in Prescience.
  5. Prescience provisions hosted employer onboarding and emails employees for missing demographics and dependents.
  6. Bolto continues daily reconciliation with GET /members and GET /account.

Mint an embed session

Response (201)
Render url in an iframe. Sessions expire after 30 minutes.
Never put the partner API key in browser code. Only the short-lived embed token belongs in the iframe URL or request header.

Embed token API

All embed endpoints accept the session token via:

Excluding employees

The iframe lets employers deselect employees from the quoting census without deleting them from Bolto’s source data. Persist this with:
Excluded employees stay in the stored census but are omitted from quoting and enrollment readiness checks.

Finalize handoff

POST /finalize creates the quote (if needed), enrolls the group with onboardingMode: "hosted", and returns:
Redirect the top-level browser window to redirectUrl so the employer can complete onboarding in Prescience. Prescience then emails employees directly to collect spouse and dependent details.

Framing configuration

Embed pages send a CSP frame-ancestors directive for Bolto origins. Override allowed ancestors with:
Per-partner overrides can also be stored on the partner record as embedAllowedOrigins from internal.getprescience.com → Partners.

Internal admin setup

Prescience ops uses the Partners tab in the internal admin portal to:
  1. Create the Bolto partner (slug: bolto)
  2. Configure iframe embed origins for Bolto staging and production hosts
  3. Enable production keys when go-live is approved
  4. Invite Bolto engineers by email to the Partner API key portal
Invited engineers sign in at internal.getprescience.com and mint their own sandbox (psk_test_...) and production (psk_live_...) keys. They cannot access other internal operations screens.