Ki Broker Trading Platform API

The same-origin REST API behind app.ki-insurance.com, the partner-gated broker trading platform where Lloyd's brokers place risks with Ki's follow algorithm. Ki publishes no reference documentation for it; the surface catalogued here was observed verbatim in the endpoint registry Ki's own client ships in its public JavaScript bundle — 102 paths and 109 operations covering quote creation and versioning, algorithmic pricing runs, schedule-of-values upload and geocoding, slip extraction jobs, firm order notes, the broker pipeline and dashboard, leads, users, broking houses and branches, nominated lead syndicates and insurers, Lloyd's risk codes and a large class-of-business master-data surface. Every call carries an Auth0-issued bearer token (issuer https://login.ki-insurance.com/, audience https://api.ki.com); there is no self-serve access.

Documentation

Specifications

Other Resources

OpenAPI Specification

ki-insurance-broker-platform-openapi.yml Raw ↑
openapi: 3.1.0
info:
  title: Ki Broker Trading Platform API (observed)
  version: '2026-07-25'
  summary: Observed HTTP surface of Ki's partner-gated broker trading platform.
  description: '**This is an API Evangelist DERIVED specification, not a Ki-published document.**


    Ki (Lloyd''s Syndicate 1618) publishes no developer portal, no API reference and no OpenAPI. This
    document was derived on 2026-07-25 from the endpoint registry that Ki''s own broker platform ships
    in its public JavaScript bundle at `https://app.ki-insurance.com/assets/index-DgeF7w2c.js`. Every
    path and every HTTP method below was observed verbatim in that bundle, together with the request helpers
    (`GET`/`POST`/`PUT`/`DELETE`) that call them.


    What is REAL here: path templates, HTTP methods, query-parameter names, the `Authorization: Bearer`
    scheme, the `application/json` content negotiation, and the 401/403/503 handling the client implements.


    What is NOT specified: request and response schemas. Ki does not publish them and they are left empty
    rather than invented. Path-parameter NAMES are assigned by API Evangelist because the minified bundle
    does not retain them.


    The API is partner-gated: access requires an Auth0 authorization-code login at `https://login.ki-insurance.com/`
    against audience `https://api.ki.com`. There is no self-serve signup.'
  contact:
    name: Ki Insurance
    url: https://ki-insurance.com/
  x-apievangelist-derivation:
    method: derived
    source: https://app.ki-insurance.com/assets/index-DgeF7w2c.js
    observed: '2026-07-25'
    note: Not a provider-published specification. Do not treat as a Ki contract.
  x-observed-endpoints-unmapped:
  - path: /api/user/current/logout
    registry_key: user.logout
    note: endpoint observed in the client registry; HTTP method not determinable from the minified bundle
  - path: /api/quote/{p1}/sov
    registry_key: quote.uploadSov
    note: endpoint observed in the client registry; HTTP method not determinable from the minified bundle
  - path: /api/quote/{p1}/pdf/subjectivities
    registry_key: subjectivities
    note: endpoint observed in the client registry; HTTP method not determinable from the minified bundle
  - path: /api/umr/master-line-slip
    registry_key: uniqueMarketReference.masterLineSlip
    note: endpoint observed in the client registry; HTTP method not determinable from the minified bundle
  - path: /api/indications/consents
    registry_key: indicationsConsent.list
    note: endpoint observed in the client registry; HTTP method not determinable from the minified bundle
  - path: /api/indications/affirm
    registry_key: indicationsConsent.consent
    note: endpoint observed in the client registry; HTTP method not determinable from the minified bundle
servers:
- url: https://app.ki-insurance.com
  description: Ki broker trading platform (same-origin API; partner-gated)
security:
- auth0Bearer: []
components:
  securitySchemes:
    auth0Bearer:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: 'Auth0-issued access token. The client attaches `Authorization: Bearer <token>` to
        every call. Issuer `https://login.ki-insurance.com/`, audience `https://api.ki.com`.'
    auth0OpenId:
      type: openIdConnect
      openIdConnectUrl: https://login.ki-insurance.com/.well-known/openid-configuration
      description: Auth0 OIDC discovery for the partner login (authorization code + PKCE).
  responses:
    Unauthorized:
      description: Unauthorized. The client clears the session and returns the user to login.
    Forbidden:
      description: Forbidden. The client routes the user to the forbidden page.
    Maintenance:
      description: Service unavailable. The client routes the user to the maintenance page.
tags:
- name: Administration
- name: Broking Houses
- name: Classes of Business
- name: Configuration
- name: Dashboard
- name: Facilities
- name: Indications
- name: Leads
- name: Market Leaders
- name: Market References
- name: Master Data
- name: Pipeline
- name: Platform
- name: Quotes
- name: Risk Codes
- name: Schedule of Values
- name: Slip Extraction
- name: Support
- name: Telemetry
- name: Users
paths:
  /api/brokinghouse/get-lloyds-broker-id:
    get:
      operationId: getBrokingHouseLloydsBrokerId
      summary: Resolve a Lloyd's broker id from broker code and pseudonym
      description: Observed in the Ki broker platform client bundle as `brokingHouse.lloydsBrokerId` ->
        `GET /api/brokinghouse/get-lloyds-broker-id?brokerCode=${e}&brokerPseudonym=${t}`. Request and
        response schemas are not published by Ki and are deliberately left unspecified rather than invented.
      tags:
      - Broking Houses
      x-observed-registry-key: brokingHouse.lloydsBrokerId
      x-observed-method-evidence: explicit GET helper call site
      x-observed-confidence: high
      responses:
        '200':
          description: Successful response. Ki does not publish the response schema.
          content:
            application/json:
              schema: {}
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '503':
          $ref: '#/components/responses/Maintenance'
      parameters:
      - name: brokerCode
        in: query
        required: false
        schema:
          type: string
        description: Query parameter observed verbatim in the published client bundle.
      - name: brokerPseudonym
        in: query
        required: false
        schema:
          type: string
        description: Query parameter observed verbatim in the published client bundle.
  /api/brokinghouse/suggest:
    get:
      operationId: getBrokingHouseSuggest
      summary: Type-ahead search for broking houses
      description: Observed in the Ki broker platform client bundle as `brokingHouse.suggest` -> `GET
        /api/brokinghouse/suggest?query=${e}`. Request and response schemas are not published by Ki and
        are deliberately left unspecified rather than invented.
      tags:
      - Broking Houses
      x-observed-registry-key: brokingHouse.suggest
      x-observed-method-evidence: explicit GET helper call site
      x-observed-confidence: high
      responses:
        '200':
          description: Successful response. Ki does not publish the response schema.
          content:
            application/json:
              schema: {}
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '503':
          $ref: '#/components/responses/Maintenance'
      parameters:
      - name: query
        in: query
        required: false
        schema:
          type: string
        description: Query parameter observed verbatim in the published client bundle.
  /api/brokinghouse/{brokingHouseId}/branch:
    post:
      operationId: createBrokingHouseBranches
      summary: Create a branch for a broking house
      description: Observed in the Ki broker platform client bundle as `brokingHouse.branches` -> `POST
        /api/brokinghouse/${e}/branch` (with an optional `?validToba=true` suffix). Request and response
        schemas are not published by Ki and are deliberately left unspecified rather than invented.
      tags:
      - Broking Houses
      x-observed-registry-key: brokingHouse.branches
      x-observed-method-evidence: explicit POST helper call site
      x-observed-confidence: high
      responses:
        '200':
          description: Successful response. Ki does not publish the response schema.
          content:
            application/json:
              schema: {}
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '503':
          $ref: '#/components/responses/Maintenance'
      parameters:
      - name: brokingHouseId
        in: path
        required: true
        schema:
          type: string
      - name: validToba
        in: query
        required: false
        schema:
          type: boolean
        description: 'Observed verbatim in the client bundle: when set the client appends ?validToba=true.'
      requestBody:
        required: true
        description: JSON request body. Ki does not publish the request schema.
        content:
          application/json:
            schema: {}
  /api/brokinghouse/{brokingHouseId}/branch/{branchId}:
    delete:
      operationId: deleteBrokingHouseBranch
      summary: Update a broking-house branch
      description: Observed in the Ki broker platform client bundle as `brokingHouse.branch` -> `DELETE
        /api/brokinghouse/${e}/branch/${t}`. Request and response schemas are not published by Ki and
        are deliberately left unspecified rather than invented.
      tags:
      - Broking Houses
      x-observed-registry-key: brokingHouse.branch
      x-observed-method-evidence: explicit DELETE helper call site
      x-observed-confidence: high
      responses:
        '200':
          description: Successful response. Ki does not publish the response schema.
          content:
            application/json:
              schema: {}
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '503':
          $ref: '#/components/responses/Maintenance'
      parameters: &id001
      - name: brokingHouseId
        in: path
        required: true
        schema:
          type: string
      - name: branchId
        in: path
        required: true
        schema:
          type: string
    put:
      operationId: updateBrokingHouseBranch
      summary: Update a broking-house branch
      description: Observed in the Ki broker platform client bundle as `brokingHouse.branch` -> `PUT /api/brokinghouse/${e}/branch/${t}`.
        Request and response schemas are not published by Ki and are deliberately left unspecified rather
        than invented.
      tags:
      - Broking Houses
      x-observed-registry-key: brokingHouse.branch
      x-observed-method-evidence: explicit PUT helper call site
      x-observed-confidence: high
      responses:
        '200':
          description: Successful response. Ki does not publish the response schema.
          content:
            application/json:
              schema: {}
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '503':
          $ref: '#/components/responses/Maintenance'
      parameters: *id001
      requestBody:
        required: true
        description: JSON request body. Ki does not publish the request schema.
        content:
          application/json:
            schema: {}
  /api/brokinghouse/{brokingHouseId}/cobs:
    get:
      operationId: getClassOfBusinessBrokerClassOfBusiness
      summary: List classes of business for a broking house
      description: Observed in the Ki broker platform client bundle as `classOfBusiness.brokerClassOfBusiness`
        -> `GET /api/brokinghouse/${e}/cobs`. Request and response schemas are not published by Ki and
        are deliberately left unspecified rather than invented.
      tags:
      - Broking Houses
      x-observed-registry-key: classOfBusiness.brokerClassOfBusiness
      x-observed-method-evidence: call-site proximity in the client bundle
      x-observed-confidence: medium
      responses:
        '200':
          description: Successful response. Ki does not publish the response schema.
          content:
            application/json:
              schema: {}
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '503':
          $ref: '#/components/responses/Maintenance'
      parameters:
      - name: brokingHouseId
        in: path
        required: true
        schema:
          type: string
  /api/cob:
    get:
      operationId: getClassOfBusiness
      summary: List classes of business
      description: Observed in the Ki broker platform client bundle as `classOfBusiness.classOfBusiness`
        -> `GET /api/cob`. Request and response schemas are not published by Ki and are deliberately left
        unspecified rather than invented.
      tags:
      - Classes of Business
      x-observed-registry-key: classOfBusiness.classOfBusiness
      x-observed-method-evidence: explicit GET helper call site
      x-observed-confidence: high
      responses:
        '200':
          description: Successful response. Ki does not publish the response schema.
          content:
            application/json:
              schema: {}
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '503':
          $ref: '#/components/responses/Maintenance'
  /api/company-markets-config/{classOfBusinessId}:
    get:
      operationId: getCompanyMarketsConfig
      summary: Retrieve company-markets configuration for a class of business
      description: Observed in the Ki broker platform client bundle as `companyMarkets.config` -> `GET
        /api/company-markets-config/${e}`. Request and response schemas are not published by Ki and are
        deliberately left unspecified rather than invented.
      tags:
      - Market Leaders
      x-observed-registry-key: companyMarkets.config
      x-observed-method-evidence: explicit GET helper call site
      x-observed-confidence: high
      responses:
        '200':
          description: Successful response. Ki does not publish the response schema.
          content:
            application/json:
              schema: {}
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '503':
          $ref: '#/components/responses/Maintenance'
      parameters:
      - name: classOfBusinessId
        in: path
        required: true
        schema:
          type: string
  /api/config/lineslips:
    get:
      operationId: getConfigLineslips
      summary: Retrieve line-slip configuration
      description: Observed in the Ki broker platform client bundle as `config.lineslips` -> `GET /api/config/lineslips`.
        Request and response schemas are not published by Ki and are deliberately left unspecified rather
        than invented.
      tags:
      - Configuration
      x-observed-registry-key: config.lineslips
      x-observed-method-evidence: explicit GET helper call site
      x-observed-confidence: high
      responses:
        '200':
          description: Successful response. Ki does not publish the response schema.
          content:
            application/json:
              schema: {}
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '503':
          $ref: '#/components/responses/Maintenance'
  /api/contact/user-request:
    post:
      operationId: createContactUserRequest
      summary: Submit a user support request
      description: Observed in the Ki broker platform client bundle as `contact.userRequest` -> `POST
        /api/contact/user-request`. Request and response schemas are not published by Ki and are deliberately
        left unspecified rather than invented.
      tags:
      - Support
      x-observed-registry-key: contact.userRequest
      x-observed-method-evidence: explicit POST helper call site
      x-observed-confidence: high
      responses:
        '200':
          description: Successful response. Ki does not publish the response schema.
          content:
            application/json:
              schema: {}
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '503':
          $ref: '#/components/responses/Maintenance'
      requestBody:
        required: true
        description: JSON request body. Ki does not publish the request schema.
        content:
          application/json:
            schema: {}
  /api/dashboard/indications:
    get:
      operationId: getDashboardIndications
      summary: Retrieve dashboard indications
      description: Observed in the Ki broker platform client bundle as `dashboard.indications` -> `GET
        /api/dashboard/indications?days=${e}&useDomainModelBasedIndications=${t}`. Request and response
        schemas are not published by Ki and are deliberately left unspecified rather than invented.
      tags:
      - Dashboard
      x-observed-registry-key: dashboard.indications
      x-observed-method-evidence: call-site proximity in the client bundle
      x-observed-confidence: medium
      responses:
        '200':
          description: Successful response. Ki does not publish the response schema.
          content:
            application/json:
              schema: {}
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '503':
          $ref: '#/components/responses/Maintenance'
      parameters:
      - name: days
        in: query
        required: false
        schema:
          type: string
        description: Query parameter observed verbatim in the published client bundle.
      - name: useDomainModelBasedIndications
        in: query
        required: false
        schema:
          type: string
        description: Query parameter observed verbatim in the published client bundle.
  /api/dashboard/renewals:
    get:
      operationId: getDashboardRenewals
      summary: Retrieve dashboard renewals
      description: Observed in the Ki broker platform client bundle as `dashboard.renewals` -> `GET /api/dashboard/renewals?days=${e}&useDomainModelBasedIndications=${t}`.
        Request and response schemas are not published by Ki and are deliberately left unspecified rather
        than invented.
      tags:
      - Dashboard
      x-observed-registry-key: dashboard.renewals
      x-observed-method-evidence: call-site proximity in the client bundle
      x-observed-confidence: medium
      responses:
        '200':
          description: Successful response. Ki does not publish the response schema.
          content:
            application/json:
              schema: {}
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '503':
          $ref: '#/components/responses/Maintenance'
      parameters:
      - name: days
        in: query
        required: false
        schema:
          type: string
        description: Query parameter observed verbatim in the published client bundle.
      - name: useDomainModelBasedIndications
        in: query
        required: false
        schema:
          type: string
        description: Query parameter observed verbatim in the published client bundle.
  /api/facilities/attestations:
    get:
      operationId: getFacilityAttestations
      summary: Retrieve facility attestations
      description: Observed in the Ki broker platform client bundle as `facilityAttestations` -> `GET
        /api/facilities/attestations?facilityId=${e}&cobId=${t}`. Request and response schemas are not
        published by Ki and are deliberately left unspecified rather than invented.
      tags:
      - Facilities
      x-observed-registry-key: facilityAttestations
      x-observed-method-evidence: call-site proximity in the client bundle
      x-observed-confidence: medium
      responses:
        '200':
          description: Successful response. Ki does not publish the response schema.
          content:
            application/json:
              schema: {}
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '503':
          $ref: '#/components/responses/Maintenance'
      parameters:
      - name: facilityId
        in: query
        required: false
        schema:
          type: string
        description: Query parameter observed verbatim in the published client bundle.
      - name: cobId
        in: query
        required: false
        schema:
          type: string
        description: Query parameter observed verbatim in the published client bundle.
  /api/facilities/exclusion-clauses:
    get:
      operationId: getExclusionClausesList
      summary: List exclusion clauses for a class of business and facility
      description: Observed in the Ki broker platform client bundle as `exclusionClauses.list` -> `GET
        /api/facilities/exclusion-clauses?cobId=${e}&facilityId=${t}`. Request and response schemas are
        not published by Ki and are deliberately left unspecified rather than invented.
      tags:
      - Facilities
      x-observed-registry-key: exclusionClauses.list
      x-observed-method-evidence: call-site proximity in the client bundle
      x-observed-confidence: medium
      responses:
        '200':
          description: Successful response. Ki does not publish the response schema.
          content:
            application/json:
              schema: {}
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '503':
          $ref: '#/components/responses/Maintenance'
      parameters:
      - name: cobId
        in: query
        required: false
        schema:
          type: string
        description: Query parameter observed verbatim in the published client bundle.
      - name: facilityId
        in: query
        required: false
        schema:
          type: string
        description: Query parameter observed verbatim in the published client bundle.
  /api/facilities/lineslip-mappings:
    get:
      operationId: getFacilitiesLineslipMappings
      summary: List facility line-slip mappings
      description: Observed in the Ki broker platform client bundle as `facilities.lineslipMappings` ->
        `GET /api/facilities/lineslip-mappings`. Request and response schemas are not published by Ki
        and are deliberately left unspecified rather than invented.
      tags:
      - Facilities
      x-observed-registry-key: facilities.lineslipMappings
      x-observed-method-evidence: explicit GET helper call site
      x-observed-confidence: high
      responses:
        '200':
          description: Successful response. Ki does not publish the response schema.
          content:
            application/json:
              schema: {}
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '503':
          $ref: '#/components/responses/Maintenance'
  /api/facilities/triggerMarkets/{classOfBusinessId}:
    get:
      operationId: getSyndicateTrackerSyndicates
      summary: List tracker/trigger markets for a class of business
      description: Observed in the Ki broker platform client bundle as `syndicate.trackerSyndicates` ->
        `GET /api/facilities/triggerMarkets/${e}`. Request and response schemas are not published by Ki
        and are deliberately left unspecified rather than invented.
      tags:
      - Facilities
      x-observed-registry-key: syndicate.trackerSyndicates
      x-observed-method-evidence: explicit GET helper call site
      x-observed-confidence: high
      responses:
        '200':
          description: Successful response. Ki does not publish the response schema.
          content:
            application/json:
              schema: {}
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '503':
          $ref: '#/components/responses/Maintenance'
      parameters:
      - name: classOfBusinessId
        in: path
        required: true
        schema:
          type: string
  /api/frontend-metrics:
    post:
      operationId: createFrontendMetrics
      summary: Submit front-end metrics
      description: Observed in the Ki broker platform client bundle as `frontendMetrics` -> `POST /api/frontend-metrics`.
        Request and response schemas are not published by Ki and are deliberately left unspecified rather
        than invented.
      tags:
      - Telemetry
      x-observed-registry-key: frontendMetrics
      x-observed-method-evidence: explicit POST helper call site
      x-observed-confidence: high
      responses:
        '200':
          description: Successful response. Ki does not publish the response schema.
          content:
            application/json:
              schema: {}
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '503':
          $ref: '#/components/responses/Maintenance'
      requestBody:
        required: true
        description: JSON request body. Ki does not publish the request schema.
        content:
          application/json:
            schema: {}
  /api/indications/suggestions-all:
    get:
      operationId: getIndicationSuggestionsLegacy
      summary: Suggest indications for an insured (pre-v2 path)
      description: Observed in the Ki broker platform client bundle as `quote.indicationSuggestions` ->
        `GET api/indications/suggestions-all`. Request and response schemas are not published by Ki and
        are deliberately left unspecified rather than invented. This is the pre-v2 path; the client selects
        between it and /api/indications/v2/suggestions-all with a LaunchDarkly feature flag.
      tags:
      - Indications
      x-observed-registry-key: quote.indicationSuggestions
      x-observed-method-evidence: explicit GET helper call site
      x-observed-confidence: high
      responses:
        '200':
          description: Successful response. Ki does not publish the response schema.
          content:
            application/json:
              schema: {}
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '503':
          $ref: '#/components/responses/Maintenance'
  /api/indications/v2/suggestions-all:
    get:
      operationId: getQuoteIndicationSuggestions
      summary: Suggest indications for an insured
      description: Observed in the Ki broker platform client bundle as `quote.indicationSuggestions` ->
        `GET api/indications/v2/suggestions-all`. Request and response schemas are not published by Ki
        and are deliberately left unspecified rather than invented.
      tags:
      - Indications
      x-observed-registry-key: quote.indicationSuggestions
      x-observed-method-evidence: explicit GET helper call site
      x-observed-confidence: high
      responses:
        '200':
          description: Successful response. Ki does not publish the response schema.
          content:
            application/json:
              schema: {}
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '503':
          $ref: '#/components/responses/Maintenance'
  /api/leads:
    get:
      operationId: getLeadsList
      summary: List leads
      description: Observed in the Ki broker platform client bundle as `leads.list` -> `GET /api/leads`.
        Request and response schemas are not published by Ki and are deliberately left unspecified rather
        than invented.
      tags:
      - Leads
      x-observed-registry-key: leads.list
      x-observed-method-evidence: explicit GET helper call site
      x-observed-confidence: high
      responses:
        '200':
          description: Successful response. Ki does not publish the response schema.
          content:
            application/json:
              schema: {}
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '503':
          $ref: '#/components/responses/Maintenance'
  /api/leads/{leadId}:
    get:
      operationId: getLeadsLead
      summary: Retrieve a lead
      description: Observed in the Ki broker platform client bundle as `leads.lead` -> `GET /api/leads/${e}`.
        Request and response schemas are not published by Ki and are deliberately left unspecified rather
        than invented.
      tags:
      - Leads
      x-observed-registry-key: leads.lead
      x-observed-method-evidence: call-site proximity in the client bundle
      x-observed-confidence: medium
      responses:
        '200':
          description: Successful response. Ki does not publish the response schema.
          content:
            application/json:
              schema: {}
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '503':
          $ref: '#/components/responses/Maintenance'
      parameters:
      - name: leadId
        in: path
        required: true
        schema:
          type: string
  /api/leads/{leadId}/activate:
    post:
      operationId: createLeadsActivate
      summary: Activate a lead
      description: Observed in the Ki broker platform client bundle as `leads.activate` -> `POST /api/leads/${e}/activate`.
        Request and response schemas are not published by Ki and are deliberately left unspecified rather
        than invented.
      tags:
      - Leads
      x-observed-registry-key: leads.activate
      x-observed-method-evidence: explicit POST helper call site
      x-observed-confidence: high
      responses:
        '200':
          description: Successful response. Ki does not publish the response schema.
          content:
            application/json:
              schema: {}
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '503':
          $ref: '#/components/responses/Maintenance'
      parameters:
      - name: leadId
        in: path
        required: true
        schema:
          type: string
      requestBody:
        required: true
        description: JSON request body. Ki does not publish the request schema.
        content:
          application/json:
            schema: {}
  /api/masterdata/compliance/search:
    get:
      operationId: getMasterdataCompliance
      summary: Search compliance master data
      description: Observed in the Ki broker platform client bundle as `masterdata.compliance` -> `GET
        /api/masterdata/compliance/search?iso2=${e}&query=${t}`. Request and response schemas are not
        published by Ki and are deliberately left unspecified rather than invented.
      tags:
      - Master Data
      x-observed-registry-key: masterdata.compliance
      x-observed-method-evidence: explicit GET helper call site
      x-observed-confidence: high
      responses:
        '200':
          description: Successful response. Ki does not publish the response schema.
          content:
            application/json:
              schema: {}
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '503':
          $ref: '#/components/responses/Maintenance'
      parameters:
      - name: iso2
        in: query
        required: false
        schema:
          type: string
        description: Query parameter observed verbatim in the published client bundle.
      - name: query
        in: query
        required: false
        schema:
          type: string
        description: Query parameter observed verbatim in the published client bundle.
  /api/masterdata/ki/cargointeresttypes:
    get:
      operationId: getMasterdataCargoInterests
      summary: Get interests
      description: Observed in the Ki broker platform client bundle as `masterdata.cargo.interests` ->
        `GET /api/masterdata/ki/cargointeresttypes`. Request and response schemas are not published by
        Ki and are deliberately left unspecified rather than invented.
      tags:
      - Master Data
      x-observed-registry-key: masterdata.cargo.interests
      x-observed-method-evidence: explicit GET helper call site
      x-observed-confidence: high
      responses:
        '200':
          description: Successful response. Ki does not publish the response schema.
          content:
            application/json:
              schema: {}
        '401':
          $ref: '#/

# --- truncated at 32 KB (123 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/ki-insurance/refs/heads/main/openapi/ki-insurance-broker-platform-openapi.yml