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

PPL Section API

Enables the creation and management of Contract sections, as structured data. Each Section represents of a specific partition of the overall risk to be insured. A section can be based upon the cover type, coverage (e.g. class of business), geographic territory and / or layer (limit of liability).

PPL Section API is one of 13 APIs that PPL publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Section. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 5 operations across 2 paths, and defines 18 schemas. It is described by OpenAPI 3.2.0, at version 1.

Requests are made against a single base URL, https://sand-api.londonmarketgroup.co.uk/ppl/nextgen/placements.

5 operations 2 paths 18 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1
Base URL
https://api.londonmarketgroup.co.uk/ppl/nextgen/placements/v1
Resource Areas
1

Paths & Operations 5

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

section 5

Enables the creation and management of Contract sections, as structured data. Each Section represents of a specific partition of the overall risk to be insured. A section can be b…

GET
/contracts/{contractId}/sections
Returns a list of Section records, within a single Contract record. This returned list is a subset of all Section record fields, based upon various query parameters.
Section_GetAll_v1 7 params → 200400401404414429500
POST
/contracts/{contractId}/sections
Creates a Section record under the Contract, representing a specific partition of the overall risk and / or coverage to be insured.
Section_Post_v1 3 params body → 200400401404414429500
GET
/contracts/{contractId}/sections/{sectionId}
Returns a single Section record. This record will contain all the Section-related structured data.
Section_GetById_v1 4 params → 200400401404414429500
PUT
/contracts/{contractId}/sections/{sectionId}
Updates a Section record, where the record is in a state that enables its update.
Section_Put_v1 5 params body → 200400401404414429500
DELETE
/contracts/{contractId}/sections/{sectionId}
Deletes a Section record, where the record is in a state that enables its deletion.
Section_Delete_v1 4 params → 200400401404414429500

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are section_getbyid (32 properties), section_postput (21 properties), section_getall (20 properties), section_premium (8 properties). Each schema is shown below with its type and property counts.

metadata_user
object
The User information of the Metadata User.
3 properties 1 required
section_excess
object
A collection of data items that represents the Excess(es) applicable prior to any liability the insurer has agreed to cover under the terms of the insurance Co…
6 properties 4 required
section_postput
object
Section structure for creates and updates
21 properties 4 required
response_sections_getall
object
5 properties
metadata
object
A collection of data items to support the creation and update of record entities.
6 properties 6 required
error
object
4 properties
section_getbyid
object
The default section of the contract represents the summary of the overall risk to be insured under the Contract.
32 properties 12 required
section_premium
object
A collection of data items that represents the financial amount to cover the risk(s) under the terms of the insurance Contract or Section.
8 properties 2 required
period
object
A collection of data items to denote the Contract or Section period.
2 properties
period_range
object
A collection of data items to denote the Contract or Section period, as a numeric and unit of measurement.
2 properties 2 required
section_getall
object
The default section of the contract represents the summary of the overall risk to be insured under the Contract.
20 properties 11 required
section_deductible
object
A collection of data items that represent the deductible(s) that are applied against the payment of a claim, within a Contract or Section.
6 properties 4 required
error_document
object
The error document.
1 property
period_date
object
A collection of data items to denote the Contract or Section period using specific dates.
4 properties 2 required
geographic_coverage
object
A collection of data items to represent the territory of cover for a Contract or Section.
3 properties 2 required
section_binding_information
object
The Binding Information relevant to a Contract or Section.
1 property
section_risk
object
A collection of data items to represent the regulatory risk classification for a Contract or Section. Only supports Lloyds Agency Type Risk Codes.
2 properties 2 required
section_limit
object
A collection of data items that represents the Limit(s) of any liability the insurer has agreed to cover under the terms of the insurance Contract or Section.
6 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ppl-london-market-section-api-openapi.yml Raw ↑

Other APIs PPL publishes across the network.

PPL Contract API
PPL Document API
PPL Health API
PPL Negotiation API
PPL Notification API
PPL Organisation API
PPL Participation API
PPL Placement API
PPL Programme API
PPL Submission API
PPL Transaction API
PPL Version API
Where this information came from

This is an independent, third-party profile of PPL Section 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.