Enables the creation, management and processing of Open Market Underwriters and Facility Panel Underwriters that are willing to participate in the underwriting of an insured's asset or liability, represented within the un/structured information in a Contract or Section.
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.
participation 5
Enables the creation, management and processing of Open Market Underwriters and Facility Panel Underwriters that are willing to participate in the underwriting of an insured's ass…
Returns a list of Participation records, within a single Section. This returned list is based upon various query parameters. Pagination functionality is supported on this operation.
Creates Participation records representing either a single Open Market Underwriter and the Carrier Stamps they are permitted to use, or a multiple of Participation records representing each Underwrit…
Returns a single Participation record. This record will contain the underwriter attributes for underwriting a risk, as well as any facility panel information, where the Underwriter's involvement is m…
Updates a Participation record, where the record is in a state that enables its update. Where an Underwriter update involves an update upon a Facility Panel, all involved Participations of said Facil…
The contract defines 34 schemas that model the data the API accepts and returns. The most detailed are participation_getbyid (30 properties), stamp_get (13 properties), subjectivity_get (7 properties), participation_put (7 properties). Each schema is shown below with its type and property counts.
participation_put
object
Participation structure for updates
7 properties
response_participations_getall_post
object
2 properties2 required
reference_get
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
line_condition_get
object
The Line Condition information, identifying the Line Condition itself, the status of its agreement.
4 properties4 required
broker_team_org_company
object
The team information of the Broker Team responsible for the node.
4 properties4 required
subjectivity_get
object
The Subjectivity information, identifying the Subjectivity itself, the status of cover prior to its agreement/satisfaction and any deadline applied to satisfy.
7 properties5 required
written_facility
object
The written underwriting line information, that the Underwriter is willing to accept, from the original master facility participation.
3 properties
participation_role
object
A mapping between Participation and Participation Role Type. This allows multiple roles to be captured against a single participation, for example both Slip Le…
2 properties2 required
participation_post
object
Participation structure for creates
5 properties
master_facility_get
object
The Master Facility information, holding original master facility information.
3 properties3 required
facility_roles
object
The facility role information that the Declaration Underwriter takes part in through their Participation.
2 properties2 required
participation_getbyid
object
Participation information
30 properties13 required
underwriter_team
object
The Team information of the Underwriter Team responsible for the Participation.
4 properties4 required
sub_panel_get
object
The sub panel information, identifying a group of Participations with a common set of underwriting terms.
3 properties3 required
stamp_get
object
The Stamp information, identifying information about the underwriting entity, roles and line references to said underwriting.
13 properties5 required
signed_facility
object
The signed line information, that the Broker has confirmed to the Underwriter, from the original master facility participation.
1 property
metadata_user
object
The User information of the Metadata User.
3 properties1 required
team_user
object
The User information of the User.
3 properties1 required
broker_user
object
The User information of the responsible Broker User.
3 properties3 required
underwriter_user_participation
object
The User information of the Underwriter User responsible for the Participation.
4 properties1 required
proposed_panel
object
The proposed underwriting line information, that the Broker is proposing to the Underwriter for this facility.
3 properties
written
object
The written underwriting line information, that the Underwriter is willing to accept.
5 properties1 required
facility_panel_put
object
The Facility Panel information, holding values from the Master Facility as a whole. This information will be consistent across all Participation records which…
3 properties3 required
signed
object
The signed line information, that the Broker has confirmed to the Underwriter.
2 properties2 required
facility_panel_get
object
The Facility Panel information, holding values from the Master Facility as a whole. This information will be consistent across all Participation records which…
4 properties4 required
proposed
object
The proposed underwriting line information, that the Broker is proposing to the Underwriter.
7 properties
metadata
object
A collection of data items to support the creation and update of record entities.
6 properties6 required
error
object
4 properties
error_document
object
The error document.
1 property
response_participations_getall
object
5 properties5 required
sub_panel_postput
object
The sub panel information, identifying a group of Participations with a common set of underwriting terms.
1 property1 required
calculated
object
The calculated signing down information, following the Broker invoking the signing down process in the Section.
1 property1 required
stamp_postput
object
The Stamp information, identifying information about the underwriting entity, roles and line references to said underwriting.
1 property1 required
facility_panel_post
object
The Facility Panel information, holding values from the Master Facility as a whole. This information will be consistent across all Participation records which…
3 properties2 required
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 Participation 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.
