How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Root Insurance Applications API

The Applications API from Root Insurance — 16 operation(s) for applications.

Root Insurance Applications API is one of 19 APIs that Root Insurance publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Application. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.

This API exposes 22 operations across 16 paths, and defines 22 schemas. It is described by OpenAPI 3.2.0, at version 1.0.1.

Requests are made against 4 base URLs: https://sandbox.uk.rootplatform.com/v1/insurance, https://api.uk.rootplatform.com/v1/insurance, https://sandbox.rootplatform.com/v1/insurance, https://api.rootplatform.com/v1/insurance.

22 operations 16 paths 22 schemas 10 GET10 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.1
Base URL
https://api.rootplatform.com/
Authentication
HTTP Basic
Terms of Service
Resource Areas
1

Authentication & Security 1

Root Insurance Applications API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

Paths & Operations 22

Across 16 paths, the API surfaces 22 operations — 10 GET, 10 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Applications 22
POST
/applications
Create an application
create-application body → 200
GET
/applications
List all applications
fetch-applications 9 params → 200
GET
/applications/{application_id}
Retrieve an application
retrieve-an-application 2 params → 200
PUT
/applications/{application_id}
Requote an application
requote-application 1 param body → 200
POST
/applications/{application_id}/alteration-packages
Create an application alteration package
create-application-alteration-package 1 param body → 200
GET
/applications/{application_id}/alteration-packages/{alteration_package_id}
Retrieve an application alteration package
retrieve-application-alteration-package 2 params → 200
POST
/applications/{application_id}/alteration-packages/{alteration_package_id}/apply
Apply application alteration package
apply-application-alteration-package 2 params → 200
GET
/applications/{application_id}/attachments
Retrieve application attachments
retrieve-application-attachments 3 params → 200
POST
/applications/{application_id}/attachments
Add application attachment
add-application-attachments 1 param body → 200
POST
/applications/{application_id}/attachments/{attachment_id}/archive
Archive an attachment
archive-application-attachment 2 params → 200
GET
/applications/{application_id}/beneficiaries
List beneficiaries
fetch-application-beneficiaries 3 params → 200
PUT
/applications/{application_id}/beneficiaries
Update beneficiaries
update-application-beneficiaries 1 param body → 200
GET
/applications/{application_id}/notes
Retrieve application notes
retrieve-application-notes 3 params → 200
POST
/applications/{application_id}/notes
Add application notes
add-application-notes 1 param body → 200
GET
/applications/{application_id}/events
Retrieve application events
retrieve-application-events 1 param → 200
GET
/applications/{application_id}/payment-method
Retrieve application payment method
retrieve-application-payment-method 1 param → 200
POST
/applications/{application_id}/payment-method
Assign application payment method
assign-application-payment-method 1 param body → 200
POST
/applications/{application_id}/send-application-pdf-to-policyholder
Send application PDF to policyholder
send-application-pdf-to-policyholder 1 param → 200
GET
/applications/{application_id}/cancellation-reasons
Get allowed application cancellation reasons
get-application-cancellation-reasons 1 param → 200
POST
/applications/{application_id}/cancel
Cancel an application
cancel-application 1 param body → 200
POST
/applications/{application_id}/archive
Archive an application
archive-application 1 param → 200
GET
/organizations/{client_app_id}/applications/{application_id}/alteration-hooks
Retrieve application alteration hooks
retrieve-application-alteration-hooks 2 params → 200

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are policy (41 properties), application (27 properties), policyholder (26 properties), payment-method (18 properties). Each schema is shown below with its type and property counts.

quote-package
object
Quote packages are designed to be low-fidelity and fast to generate, and are used to generate and display new quotes rapidly on a customer-facing front-end. Th…
12 properties 10 required
policyholder
object
26 properties 9 required
attachment
object
7 properties 6 required
beneficiary-relationship
string
The beneficiary's relationship to the policyholder.
application-alteration-hook
object
9 properties 8 required
policy-status
string
The policy status. See the [managing policies](https://docs.rootplatform.com/docs/policy-administrationpolicy-lifecycle) guide for more details on the policy l…
notes
array
policy
object
Policies are issued from applications, and represent binding insurance agreements. Parameters stored on the policy can be referenced in custom notifications, p…
41 properties 28 required
cellphone
objectnull
null and "" allowed. Object containing the cellphone number in national format, and the corresponding alpha 2 country code.
2 properties 2 required
applications
array
payment-charge-type
string
Variable charges are applied as a proportion of the total payment amount. Fixed charges are applied as an absolute currency value in cents. The balance is the…
beneficiaries-request
array
null is allowed. An array of beneficiaries. If null, the default beneficiary may be the policyholder if enabled in the product module settings. Some modules ma…
payment-method
object
18 properties 5 required
beneficiaries
array
null is allowed. An array of beneficiaries. If null, the default beneficiary may be the policyholder if enabled in the product module settings. Some product mo…
application-alteration-packages
array
note
object
2 properties 2 required
payment-details
object
Details of the account into which the payout should be made.
2 properties 2 required
bank-name
string
The name of the bank
application
object
An application represents a "draft" policy, with all information captured and validated. Applications persist on Root (they do not expire), and can be reviewed…
27 properties 12 required
cellphone-string
stringnull
null and "" allowed. String containing the cellphone number in international format.
application-alteration-hooks
array
application-alteration-package
object
14 properties 7 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

root-applications-api-openapi.yml Raw ↑

Other APIs Root Insurance publishes across the network.

Root Bind API
Root Insurance Calls API
Root Insurance Claims API
Root Insurance Complaints API
Root Insurance Data exports API
Root Insurance Data stores API
Root Insurance Embed API
Root Insurance Files API
Root Insurance Leads API
Root Insurance Notifications API
Root Insurance Payment Methods API
Root Insurance Payments API
Where this information came from

This is an independent, third-party profile of Root Insurance Applications API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.