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

Qoala API Specification API

Policy API documentation consist of create policy, get policy detail or status, policy cancellation and policy activation.

Qoala API Specification API is one of 2 APIs that Qoala publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include API Specification. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 10 operations across 9 paths, and defines 18 schemas. It is described by OpenAPI 3.2.0, at version v1.3.

Requests are made against 3 base URLs: https://api-staging.qoala.app, https://api.uat.qoala.app, https://api.qoala.app.

10 operations 9 paths 18 schemas 3 GET2 PATCH4 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1.3
Base URL
https://api.qoala.app
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Qoala API Specification API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-api-key (ApiKeyAuth). By default, every request must be authenticated.

Paths & Operations 10

Across 9 paths, the API surfaces 10 operations — 3 GET, 2 PATCH, 4 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

API Specification 10

Policy API documentation consist of create policy, get policy detail or status, policy cancellation and policy activation.

POST
/api/v2/quotation/quotes
Create Policy
body → 200202400401404500
GET
/api/v2/quotation/quotes/partner/status
Get Policy Detail
detailPolicy 3 params → 200400401404500
PATCH
/api/v2/policies/partner/cancel
Cancel Policy
cancelPolicy body → 200400401404500
POST
/api/v2/claims/partner/create
Create Claim
createClaim body → 200400401500
PATCH
/api/v2/claims/partner/cancel
Cancel Claim
cancelClaim body → 200401500
POST
/api/v2/claims/partner/update/presign
Upload claim documents
presignCreateClaim body → 200401500
PUT
/api/v2/claims/partner/update/presign
Update claim documents
presignUploadClaim body → 200401500
GET
/api/v2/products/finance/partner/products/stoploss/{claim_pool_code}
Get Claim Pool
getPool 1 param → 200400401500
GET
/api/v2/claims/partner/status
Get Claim Status
statusClaim 2 params → 200400401404500
POST
/api/v2/policies/documents/activation
Activate Policy
activationPolicy body → 200400401500

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are InsuredTravel (23 properties), InsuredVehicle (19 properties), InsuredGadget (15 properties), PolicyHolderRequest (11 properties). Each schema is shown below with its type and property counts.

200status
object
4 properties
InsuredLoan
object
10 properties
InsuredGoods
object
8 properties 6 required
InsuredTravel
object
23 properties 6 required
Insured
object
3 properties 2 required
200detailPolicy
object
4 properties
Document_2
object
4 properties
Document
object
4 properties
InsuredVehicle
object
19 properties
InsuredUser_2
object
11 properties
Insured_2
object
3 properties 2 required
InsuredMotor
object
11 properties
PolicyHolderRequest
object
11 properties 2 required
InsuredGadget
object
15 properties 6 required
InsuredShipping
object
7 properties 2 required
InsuredUser
object
11 properties
InsuredAgent
object
8 properties 3 required
InsuredPackage
object
4 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

qoala-api-specification-api-openapi.yml Raw ↑

Other APIs Qoala publishes across the network.

Qoala Authentication API
Where this information came from

This is an independent, third-party profile of Qoala API Specification 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.