You need a test API key (
psk_test_...). Ask your Prescience partner engineer
to invite you to the Partner API key portal at
internal.getprescience.com, then mint a
sandbox key there and open Step 2 · Test integration. Sandbox keys remain
viewable and copyable in the scoped portal. Email
partners@getprescience.com if you need
help getting access.1
Check your key
Export your key and hit
/ping. It confirms the key is valid and tells you which mode you’re in.Response
2
Create a group
A group is one employer. Creating it requires exactly four values:
companyName, domain, contact.name, and contact.email. A first-time
employer does not need prior coverage or prior PEPM data.Response (201)
3
Upload the census
PUT /census replaces the full census. To quote, each member only needs a zip and one of dob | age. You almost certainly have both already. Names and emails are required later, at enrollment.This is Acme’s real census: 12 employees, 19 covered lives.Response (200)
errors with the row index while everything else is stored. Details in the census guide.4
Create the quote
One POST with an empty body returns the full quote after Prescience has the
group’s market-rate snapshot. The plan year start defaults to the first of the
month at least 60 days out.Immediately after a census update, this request can return Read it like this:
409 rates_pending
while Prescience compares local plans. Retry with backoff, or use the
Bolto iframe. In that flow, Bolto makes a separate
POST /groups/{groupId}/embed-sessions call when the employer opens the offer;
the iframe shows real progress and creates its plan model when the sweep completes.Response (201)
monthly.totalCents is the modeled all-in monthly amount,
monthly.pepmCents is the per-covered-life monthly amount, and comparison
measures Prescience against the selected platinum market benchmark. Field-by-field
details are in the quotes guide.5
Enroll the employer
When the employer accepts the quote, create the enrollment. The signatory is the employer admin who made the selection; Prescience provisions them as the company’s admin in the Prescience employer portal and runs onboarding there (the default From here, Prescience runs onboarding, KYB, banking, and plan setup with the
employer directly in the Prescience employer portal, then activation
(
onboardingMode: "hosted"; see the enrollment guide).Response (201)
sandbox → prod). No code on your side; poll
GET /enrollments/{enrollmentId} or listen for webhooks. employerPortal
confirms the signatory’s portal account: this is a test-mode key, so the normal
portal and member invitations are suppressed. The iframe’s employer
verification code is the only sandbox email. The sandbox company is fully
functional but flagged test: true and never activated; no money moves.6
Read the account
Once enrolled, The benefits tab guide maps every field to a UI element, with the full in-force payload for this group.
GET /account returns funding, premium-equivalent totals, spend by category, and savings, all aggregate and de-identified.Where to next
Read plan metadata
Static plan fields plus group-specific quote pricing.
Set up webhooks
Signed events for enrollment, activation, and finalized quotes.
Sync your census
New hires, terminations, and COBRA: one call each.
Go live
BAA, data handling, and what changes between test and live.