BackNine Insurance API

Name: BackNine Insurance API API
Brand: BackNine Insurance API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceAccountingapiKey12 EndpointsREST

For Agents

Quote life insurance, create and progress electronic applications (eApps), manage applicant access, and pull illustrations through the BackNine general agency API.

Quickstart

Get started with BackNine Insurance API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"get a life insurance quote"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with BackNine Insurance API API.

Generate life insurance quotes for an applicant via the eapp-quotes endpoint

Create new electronic applications (eApps) and resume in-progress ones via /api/v1/eapps and /resume

Grant or manage applicant and advisor access to a specific eApp via the accesses/create endpoint

Update insured data on an existing eApp before submission

GET STARTED

Start building with BackNine Insurance API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for BackNine Insurance API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for BackNine Insurance API, keeping it validated and agent-ready. BackNine is a tech-enabled general agency for life insurance, and the API exposes 12 endpoints for getting quotes, creating and resuming electronic applications (eApps), managing eApp access, updating insured data, advancing eApp steps, sending text messages to applicants, and downloading illustrations. Use it to embed life insurance quoting and application flows into agent platforms, advisor tooling, and back-office automations without rebuilding eApp infrastructure.

Use Cases

Patterns agents use BackNine Insurance API API for, with concrete tasks.

★ Embed life insurance quoting in an advisor platform

Power a financial advisor tool that runs life insurance quotes inside its own UI by calling /api/v1/eapp-quotes with applicant details. The platform then drops the user straight into a BackNine eApp through /api/v1/eapps without forcing them to bounce out to a third-party portal.

POST to /api/v1/eapp-quotes with applicant date of birth, gender, state, face amount $500,000, and product term-20, and return the top three carriers by premium.

Resume and progress in-flight applications

When applicants leave an eApp partway through, advisors can resume it via /api/v1/eapps/{eapp_uuid}/resume, update insured data, and walk the application to the next step using /step/next. This makes follow-up workflows cleaner because no application is lost between sessions.

Resume eApp 11111111-1111-1111-1111-111111111111, update the insured's height and weight on /insured, and call /step/next.

Outreach via text and illustrations

Send applicants and advisors text-message reminders during the application process via /api/v1/text and email or download illustration PDFs from /api/v1/quotes/{id}/illustration so applicants understand the policy they are buying. Combining outreach and document delivery in one API reduces hand-offs.

POST /api/v1/text with body 'Your application is 80% complete' to the applicant phone number on file for an active eApp.

Agent-driven life insurance workflows

Let an AI agent take a user request like 'get me a 20-year term quote for $1m' and run quoting, eApp creation, and insured data updates as a single workflow through Jentic. The BackNine API surface is small and well-typed, which is ideal for an agent tool that needs predictable inputs and outputs.

Search Jentic for 'get a backnine life insurance quote', load the schema for POST /api/v1/eapp-quotes, and execute it for a 35-year-old non-smoker, $1,000,000 face amount, term-20.

Key Endpoints

12 endpoints — jentic publishes the only available openapi specification for backnine insurance api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/api/v1/eapp-quotes

Get a life insurance quote

POST

/api/v1/eapps

Create a new eApp

POST

/api/v1/eapps/{eapp_uuid}/resume

Resume an in-progress eApp

POST

/api/v1/eapps/{eapp_uuid}/accesses/create

Grant access to an eApp

POST

/api/v1/eapps/{eapp_uuid}/step/next

Advance the eApp to the next step

POST

/api/v1/eapps/{eapp_uuid}/insured

Update insured data on an eApp

GET

/api/v1/quotes/{id}/illustration

Download a quote illustration

POST

/api/v1/text

Send a text message to an applicant

POST

/api/v1/eapp-quotes

Get a life insurance quote

POST

/api/v1/eapps

Create a new eApp

POST

/api/v1/eapps/{eapp_uuid}/resume

Resume an in-progress eApp

POST

/api/v1/eapps/{eapp_uuid}/accesses/create

Grant access to an eApp

POST

/api/v1/eapps/{eapp_uuid}/step/next

Advance the eApp to the next step

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The BackNine API key is stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped, short-lived credential references — the raw API key is never exposed to the agent's context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'get a life insurance quote') and Jentic returns the matching POST /api/v1/eapp-quotes operation with its full input schema, so the agent can call the right endpoint without reading BackNine docs.

Time to first call

Direct integration: 1-2 days for API key handling, eApp state modelling, and illustration download flows. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Stripe

Charge premium payments alongside an eApp submission

Use Stripe to collect any required premium or fee payments at submission time when BackNine workflows hand off to billing.

Alternative

Twilio

Programmable SMS as an alternative to BackNine's /text endpoint

Use Twilio when your platform already centralises messaging through it; use BackNine /api/v1/text when you want messaging native to the eApp record.

Complementary

SendGrid Mail

Send email reminders and illustration attachments to applicants

Use SendGrid Mail to email illustration PDFs downloaded from /api/v1/quotes/{id}/illustration to applicants and advisors.

FAQs

Specific to using BackNine Insurance API API through Jentic.

Why is there no official OpenAPI spec for BackNine Insurance API?

BackNine documents its API on docs.back9ins.com but does not publish a machine-readable OpenAPI specification. Jentic generates and maintains this spec from the BackNine documentation so that AI agents and developers can call the eApp and quoting endpoints via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the BackNine Insurance API use?

The API uses an API key passed via the `ApiKeyAuth` security scheme defined in the spec. Through Jentic the API key is stored encrypted in the vault and only injected at execution time, so the key never enters the agent's prompt or context.

Can I get a life insurance quote with this API?

Yes. POST /api/v1/eapp-quotes returns quotes for an applicant when given core fields such as date of birth, state, face amount, and product type. The same eapp_uuid can then drive POST /api/v1/eapps/{eapp_uuid}/quotes to attach quotes to an electronic application.

What are the rate limits for the BackNine API?

The spec does not declare explicit rate limits. BackNine applies limits at the account level; check your BackNine API key dashboard for the exact request-per-minute allowance applicable to your integration.

How do I create an eApp through Jentic?

Search Jentic for 'create a backnine eapp', load the schema for POST /api/v1/eapps, and execute it with the applicant payload. Install with `pip install jentic` and use the async search/load/execute pattern.

Does this API issue policies directly?

No. The API drives quoting and electronic application capture only. Underwriting, carrier issuance, and policy delivery happen at the carriers BackNine writes business with — the API ends at submission and illustration delivery.