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

The notification API from PPL — 3 operation(s) for notification.

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

Tagged areas include Notification. 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 12 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.

3 operations 3 paths 12 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.

notification 3
GET
/notifications
Returns a list of all Notification records, based upon various query parameters. Pagination functionality is supported on this operation.
Notification_GetAll_v1 21 params → 200400401404414429500
GET
/notifications/{notificationId}
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…
Notification_GetById_v1 3 params → 200400401404414429500
POST
/notifications/markAllAsRead
Initiates the operation to update all non-technical Notification records as read from a defined date.
Notification_MarkAllAsRead_v1 2 params body → 200400401404414429500

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are response_notification_record (15 properties), recipient_notifications (8 properties), references (8 properties), metadata (6 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
metadata
object
A collection of data items to support the creation and update of record entities.
6 properties 6 required
response_notification_record
object
The Notification Information record.
15 properties 9 required
error_document
object
The error document.
1 property
error
object
4 properties
references
object
Notification references structure.
8 properties 2 required
context_notification
object
Contextual information about where the subject of this Notification is within the platform.
2 properties 2 required
response_notifications
object
5 properties
response_markallasread
object
Response for notifications mark all as read endpoint.
2 properties 2 required
sender_notifications
object
The Sender information of the individual responsible for the Notification record.
5 properties 5 required
recipient_notifications
object
The Recipient information of the individual the Notification record is intended for.
8 properties 8 required
notification_markallasread
object
Payload for notifications mark all as read endpoint.
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs PPL publishes across the network.

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

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