Retrieves informative and actionable notifications about an interested party's involvement in the placement process, plus the business transaction log for contract-related engagements. Pull-based only - notifications and transactions are polled over REST; PPL publishes no webhook, callback or AsyncAPI event-push surface. OpenAPI 3.0.1, 7 paths and 7 operations.
PPL Events API is one of 5 APIs that PPL publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Event, Notification, Transaction, and Audit. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes
7 operations
across 7 paths,
organized into 4 resource areas,
and defines 35 schemas.
It is described by OpenAPI 3.0.1, at version 1.
Requests are made against a single base URL, https://sand-api.londonmarketgroup.co.uk/ppl/nextgen/events.
7 operations7 paths35 schemas6 GET1 POST
Metadata
The identity and technical contract details declared by the specification.
Across 7 paths, the API surfaces 7 operations — 6 GET, 1 POST. They span 4 resource areas: health, version, notification, transaction. Each is listed below with its method, path, parameters, and response codes.
health 1
GET
/health
Checks the health of this Notification Resource API.
Health→ 200
version 1
GET
/version
Checks the version of this Notification Resource API.
Version→ 200
notification 3
GET
/notifications
Returns a list of all Notification records, based upon various query parameters. Pagination functionality is supported on this operation.
Returns a single Notification record. This record will contain attributes pertaining to the type of notification and any type of action that is required. The context information is the subject of the…
Returns a single Transaction record. This record will contain attributes pertaining to the category and type of transaction. The content is determined upon the type of the transaction.
The contract defines 35 schemas that model the data the API accepts and returns. The most detailed are response_notification_record (15 properties), response_transaction_getbyid (14 properties), endorsement_transaction (11 properties), references (8 properties). Each schema is shown below with its type and property counts.
health
object
Health endpoint payload
1 property
version
object
Version endpoint payload
2 properties
context_notification
object
Contextual information about where the subject of this Notification is within the platform.
2 properties2 required
metadata
object
A collection of data items to support the creation and update of record entities.
6 properties6 required
metadata_user
object
The User information of the Metadata User.
3 properties1 required
notification_markallasread
object
Payload for notifications mark all as read endpoint.
1 property1 required
recipient_notifications
object
The Recipient information of the individual the Notification record is intended for.
8 properties8 required
references
object
Notification references structure.
8 properties2 required
response_markallasread
object
Response for notifications mark all as read endpoint.
2 properties2 required
response_notification_record
object
The Notification Information record.
15 properties9 required
response_notifications
object
5 properties
sender_notifications
object
The Sender information of the individual responsible for the Notification record.
5 properties5 required
attribute_transaction
object
The User information of the Recipient of the Transaction.
2 properties2 required
broker_user
object
The User information of the responsible Broker User.
3 properties3 required
comment_transaction
object
Array of comments on the subjectivities negotiation.
3 properties3 required
context_transaction
object
Contextual information about where this Transaction is generated.
6 properties4 required
document_transaction
object
Document reference
5 properties4 required
endorsement_transaction
object
A list of Endorsements relating to a single transaction.
11 properties9 required
line_condition_transaction
object
The Line Condition information, identifying the Line Condition itself, the status of its agreement.
3 properties2 required
message_endorsement_transaction
object
The message written on this Endorsement.
2 properties
message_transaction
object
Message relating to the transaction.
7 properties
metadata_transaction
object
A collection of data items to support the creation and update of record entities.
3 properties2 required
recipient_transaction
object
The User information of the Recipient of the Transaction.
5 properties5 required
reference_transaction
object
The line reference information, which captures the line references in relating to the Contract or Section that is being underwritten. Also maintain the Risk Cl…
3 properties1 required
response_transaction_getall
object
The Transaction Information record.
8 properties5 required
response_transaction_getbyid
object
The Transaction Information record.
14 properties5 required
response_transactions
object
5 properties4 required
risk_classification_transaction
object
The regulatory code(s) that are applicable to the Stamp.
2 properties2 required
satisfaction_attempt_transaction
object
A collection of data items to support Subjectivity Management information.
6 properties4 required
sender_onbehalf_transaction
object
The User information of the Sender that should have been responsible for the Transaction.
5 properties5 required
sender_transaction
object
The User information of the Author responsible for the Transaction.
5 properties5 required
stamp_transaction
object
The Stamp information, identifying information about the underwriting entity, roles and line references to said underwriting.
7 properties2 required
subjectivity_transaction
object
The Subjectivity information, identifying the Subjectivity itself, the status of cover prior to its agreement/satisfaction and any deadline applied to satisfy.
6 properties3 required
error
object
4 properties
error_document
object
The error document.
1 property
Specification
The full machine-readable OpenAPI contract behind this narrative.
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.
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 Events 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.
