The insurance API behind Olli
Rate, quote, bind and finalize a policy over REST. The same platform Olli runs on is what a partner integrates against.
Built for platforms that want insurance inside their own product rather than a link out to someone else's.
What does the API actually do?
Four stages, end to end. A customer can go from risk data to an in-force policy without leaving your product.
Rate
Submit risk data and get prices back for every program the risk is eligible for. Read-only, nothing is stored, so you can rate as often as you need while a customer is still deciding.
Quote
Turn a rate into a quote against a specific program, with the coverages, limits and deductibles the customer selected.
Bind
Bind the quote and issue the policy. Coverage starts, documents are generated, and the policy becomes serviceable through the same API.
Finalize
Payment, invoicing and settlement to the carrier. The money side is part of the platform, not something you have to assemble separately.
What sits behind the four calls
Selling a policy is the easy part. These are the pieces a platform usually discovers it needs six months in.
Appetite and eligibility
Check a class of business against live carrier appetite before you show a customer anything. The rating call only returns programs the risk actually qualifies for.
Billing and disbursements
Invoicing, payment capture, carrier settlement and partner disbursements are handled in the platform rather than left to the integrator.
Policy servicing and claims
Endorsements, cancellation, renewal and the full claims lifecycle, so a policy sold through your product stays serviceable through your product.
Bordereaux and reporting
Regulatory and carrier reporting is generated from the same records, which is usually the part a platform discovers late and has to build itself.
How does an integration work?
REST over HTTPS, JSON in and out. Any HTTP client will do.
Authentication
Partners authenticate with a scoped API key issued by Olli. Every call is bound to your account, so the data you can reach is your own.
Getting access
There is no self-serve signup. We issue credentials as part of onboarding a partner, once we have agreed what you are distributing and where. Insurance is licensed state by state, and that conversation has to happen first.
Reference documentation
Endpoints, request and response schemas, and code samples are generated from our OpenAPI specification and published at docs.api.olli.insure, so the reference matches what the API does today.
Thinking about embedding insurance?
Tell us what you are building and who your customers are. We will tell you what we can write for them and what integration would look like.