/platforms · for marketplaces & embedded distribution
Most carrier APIs stop at "get a quote." Ours covers the whole policy: rate, quote, bind, endorse, cancel, reinstate, and renew — the operations your users will actually need in month six, not just at checkout.
# 1. rate & quote
curl -X POST https://api.stratariskpartners.com/v1/quotes \
-H "x-api-key: $STRATA_KEY" \
-d '{"line":"BOP","effective":"2026-10-01","risk":{"state":"OH","class":"retail", "tiv":850000}}'
→ 200 {"quoteId":"Q-2026-1187", "premium":2210.00, "status":"bindable"}
# 2. bind
curl -X POST https://api.stratariskpartners.com/v1/quotes/Q-2026-1187/bind \
-H "x-api-key: $STRATA_KEY"
→ 201 {"policy":"BOP-2026-0001", "documents":["confirmation.html"]}// full lifecycle surface
rate + underwriting rules inline
issue + auto-generate docs
mid-term Δ, pro-rata computed
pro-rata or short-rate
lapse-aware restoration
async renewal pipeline
transactions, premium, earned
upload + retrieve, per policy
auth
Server-to-server calls use hashed x-api-key credentials; user-context flows exchange the key for a scoped JWT. Rotate keys without redeploying.
predictability
Out-of-appetite submissions return a structured 422 with rule-level reasons — so your funnel analytics know exactly why a risk didn't quote.
accounting
Every API transaction journals to the same ledgers our carriers audit. Your reconciliation exports match ours because they're the same numbers.
$ strata keys --env sandbox
If you run a commercial insurance marketplace or embed coverage in a vertical SaaS product, we'll set you up with sandbox keys, the Postman collection, and a working bind flow before the first call ends.