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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
PPL

PPL Submission API

Enables the retrieval of Submissions for Underwriters.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

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

This API exposes 3 operations across 3 paths, and defines 35 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/submissions.

3 operations 3 paths 35 schemas 2 GET1 POST

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 3

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

submission 3

Enables the retrieval of Submissions for Underwriters.

GET
/submissions
Returns a list of all Submission records based upon various query parameters. Pagination functionality is supported on this operation.
Submission_GetAll_v1 31 params → 200400401404414429500
GET
/submissions/{submissionId}
Returns a single Submission record. This record includes structured data pertaining to a single Contract offering (and any subsequent Sections, if applicable) as well as references to download (1) th…
Submission_GetById_v1 3 params → 200400401404414429500
POST
/submissions/{submissionId}/send
Initiates the operation to send the latest Underwriter responses as part of a response to a Submission back to the Broker. The outcome of each Negotiation will either (1) agree unconditionally to the…
Submission_Send_v1 3 params body → 200400401404414429500

Schemas 35

The contract defines 35 schemas that model the data the API accepts and returns. The most detailed are submission_section_getbyid (27 properties), submission_getall (14 properties), submission_contract_getbyid (14 properties), submission_getbyid (14 properties). Each schema is shown below with its type and property counts.

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
response_submissions_getall
object
5 properties 5 required
submission_contract_getall
object
A collection of insurance Contracts.
6 properties 6 required
underwriter_user
object
The User information of the Underwriter User responsible for the Participation.
3 properties 1 required
period_date
object
A collection of data items to denote the Contract or Section period using specific dates.
4 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
submission_getall
object
Submission structure for Get All
14 properties 14 required
underwriter_team_no_org
object
The Team information of the Underwriter Team responsible for the Participation.
3 properties 3 required
notification
object
The Notification information relating to the Document.
4 properties 4 required
submission_section_send
object
A representation 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) and/o…
4 properties 2 required
submission_contract_getbyid
object
A collection of insurance Contracts.
14 properties 14 required
geographic_coverage
object
A collection of data items to represent the territory of cover for a Contract or Section.
3 properties 2 required
submission_programme_getall
object
A collection of Contracts for a common purpose.
4 properties 4 required
submission_getbyid
object
Submission structure for Get by Identifier
14 properties 14 required
metadata_user
object
The User information of the Metadata User.
3 properties 1 required
broker_user
object
The User information of the responsible Broker User.
3 properties 3 required
submission_contract_send
object
A collection of insurance Contracts.
8 properties 8 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
submission_section_getall
object
A representation 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) and/o…
5 properties 5 required
submission_send_input
object
Submission input structure for Send
1 property 1 required
contract_insured
object
An individual or organisation, and their relationship within a contract of insurance.
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
submission_programme_getbyid
object
A collection of Contracts for a common purpose.
4 properties 4 required
broker_team_org_company_no_id
object
The team information of the Broker Team responsible for the node.
3 properties 3 required
metadata
object
A collection of data items to support the creation and update of record entities.
6 properties 6 required
error
object
4 properties
error_document
object
The error document.
1 property
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
submission_programme_send
object
A collection of Contracts for a common purpose.
3 properties 3 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
submission_section_getbyid
object
A representation 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) and/o…
27 properties 14 required
submission_send_output
object
Submission output structure for Send
9 properties 9 required
broker_team_company_no_id
object
The team information of the Broker Team responsible for the node.
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs PPL publishes across the network.

PPL Contract API
AE Profile APIs.io
PPL Document API
AE Profile APIs.io
PPL Health API
AE Profile APIs.io
PPL Negotiation API
AE Profile APIs.io
PPL Notification API
AE Profile APIs.io
PPL Organisation API
AE Profile APIs.io
PPL Participation API
AE Profile APIs.io
PPL Placement API
AE Profile APIs.io
PPL Programme API
AE Profile APIs.io
PPL Section API
AE Profile APIs.io
PPL Transaction API
AE Profile APIs.io
PPL Version API
AE Profile APIs.io
#Submission
← Back to P APIs
API Details
ID
ppl-london-market:ppl-london-market-submission-api
Base URL
https://api.londonmarketgroup.co.uk/ppl/nextgen/placements/v1
Docs
https://developer.pplnextgen.com/placements
Provider
PPL
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=ppl-london-market-submission-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/ppl-london-market-submission-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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