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 Transaction API

The transaction API from PPL — 2 operation(s) for transaction.

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

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

This API exposes 2 operations across 2 paths, and defines 24 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/events.

2 operations 2 paths 24 schemas 2 GET

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 2

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

transaction 2
GET
/transactions
Returns a list of all Transaction records, based upon various query parameters. Pagination functionality is supported on this operation.
Transaction_GetAll_v1 16 params → 200400401404414429500
GET
/transactions/{transactionId}
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.
Transaction_GetById_v1 3 params → 200400401404414429500

Schemas 24

The contract defines 24 schemas that model the data the API accepts and returns. The most detailed are response_transaction_getbyid (14 properties), endorsement_transaction (11 properties), response_transaction_getall (8 properties), stamp_transaction (7 properties). Each schema is shown below with its type and property counts.

attribute_transaction
object
The User information of the Recipient of the Transaction.
2 properties 2 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 properties 3 required
risk_classification_transaction
object
The regulatory code(s) that are applicable to the Stamp.
2 properties 2 required
stamp_transaction
object
The Stamp information, identifying information about the underwriting entity, roles and line references to said underwriting.
7 properties 2 required
message_endorsement_transaction
object
The message written on this Endorsement.
2 properties
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 properties 1 required
message_transaction
object
Message relating to the transaction.
7 properties
response_transaction_getall
object
The Transaction Information record.
8 properties 5 required
line_condition_transaction
object
The Line Condition information, identifying the Line Condition itself, the status of its agreement.
3 properties 2 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
endorsement_transaction
object
A list of Endorsements relating to a single transaction.
11 properties 9 required
recipient_transaction
object
The User information of the Recipient of the Transaction.
5 properties 5 required
response_transactions
object
5 properties 4 required
metadata_transaction
object
A collection of data items to support the creation and update of record entities.
3 properties 2 required
sender_transaction
object
The User information of the Author responsible for the Transaction.
5 properties 5 required
sender_onbehalf_transaction
object
The User information of the Sender that should have been responsible for the Transaction.
5 properties 5 required
context_transaction
object
Contextual information about where this Transaction is generated.
6 properties 4 required
satisfaction_attempt_transaction
object
A collection of data items to support Subjectivity Management information.
6 properties 4 required
error
object
4 properties
error_document
object
The error document.
1 property
comment_transaction
object
Array of comments on the subjectivities negotiation.
3 properties 3 required
document_transaction
object
Document reference
5 properties 4 required
response_transaction_getbyid
object
The Transaction Information record.
14 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ppl-london-market-transaction-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 Section API
PPL Submission API
PPL Version API
Where this information came from

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