ContactLiaisonSubmission
objectBroker contact liaison recorded under the producer for this submission. The platform resolves this block one of three ways:
- Update by key — supply
contactliaisonid.id(an existing liaison key). That liaison is updated in place with theemail,phoneNo, andmobilePhonevalues provided; the platform targets it directly without searching by name.firstName+lastNamemust also be supplied. - Update by name match — omit
contactliaisonid. WhenfirstName+lastNamematch an existing liaison under the producer, that liaison is updated in place. - Create — omit
contactliaisonidand supply afirstName+lastNamethat do not match any existing liaison; a new liaison is created.
firstName and lastName are required in all three cases.
Optional. Existing contact liaison key (id only). When supplied, the platform attaches that liaison and all individual fields become optional. Omit to create or update by name match.
Show Child Parameters
Required when creating a new contact (Mode B). First name of the broker contact person.
Example:John
Required when creating a new contact (Mode B). Last name of the broker contact person.
Example:Smith
Required when creating a new contact (Mode B). Email address of the liaison.
Example:Yes@example.com
Required when creating a new contact (Mode B). Office/landline phone number of the liaison.
Example:9000000000
Optional. Mobile / cell phone number of the liaison.
Example:899 898 09
Optional. Fax number of the liaison.
Example:45
Optional. State where the liaison is located. Always send as code, e.g. { “code”: “UT” }.
Example:{"code":"UT"}
Show Child Parameters
Optional. City where the liaison is located. Always send as description, e.g. { “description”: “Green Bay” }.
Example:{"description":"Green Bay"}
Show Child Parameters
Optional. Region of the liaison. Always send as description, e.g. { “description”: “GBR” }.
Example:{"description":"GBR"}
Show Child Parameters
ShellSubmissionResponse
objectIssuePolicyRequest
objectSingle-call submission payload. Combines Shell + Full + Quote + Bind data so external consumers send everything once — the platform executes each stage internally in sequence.
fullRequest is required and carries the insured/policy/producer identifiers (shell) plus underwriting enrichment (full). quoteRequest carries all pricing, section, and line data, including bind-time attributes for each section and line. bindRequest carries the policy-level bind attributes that are not tied to a specific section or line.
Required. Shell (Step 1) and Full (Step 2) data combined.
Required fields: underWriter (id), revTurnover.
Required shell fields (first submission): insured, producer, policy (effectiveDate, expiryDate, currency, product, territory), directAssumed, typeOfBilling, division, writtenLine, sectionIdentifier, referenceType, typeOfPlacementBespoke.
Optional fields: producingUnderwriter (id), producingCompany (id), lloydsIndustrialSector (id).
Per-line fields (ourRole, signedLinePercentage) belong in quoteRequest.lines[].
Show Child Parameters
Quote, FON, and bind attributes at the section and line level.
Required quote fields: sections (array, at least one), summaryCurrency (code), typeOfCyberClauseStatus (id), uSClassification (id).
Each entry in sections[] carries coverage lines, deductions, deductibles, reinstatements, regulatory coding, and bind-time attributes (instalmentbasis, paymentDays, premiumBasis, typeofClaimBasis).
Each entry in lines[] represents an agency line and carries submission fields (underWriter, typeOfBilling, division, writtenLine, producingCompany, sBFClass), quote fields (ourRole, signedLinePercentage, producingUnderwriter, lloydsPlatform, bureauLead, isThirdPartyCapacityDeployed), FON fields (brokerOrderPercent, signedOrderPercent, policyLineReference), and bind fields (claimsAgreementParty, defenseCostsCovered, leaderPercent, leaderReference, actualDateWritten, dateSigned, policyLineReferenceOverride). Syndicate lines and derived fields (originating division/office, global-risk cross-reference, inclusive line) are handled by Trident.
Show Child Parameters
Policy-level bind attributes —
Key required fields: prebindSanctionCheckComplete.
Supply insured for bind-time enrichment (occupation, mailing address, TINs). Supply surplusBroker when risk premium originates from the United States. Supply fon for FON activity attributes (CY LOB only).
claimsAgreementParty is a per-line attribute — supply it on each entry in quoteRequest.lines[], not here.
Section/line attributes (premiumBasis, typeofClaimBasis, instalmentbasis, leaderPercent, etc.) are carried in quoteRequest — not repeated here.
Show Child Parameters
BindRequest
objectPolicy-level bind attributes. Supply everything that does not belong to a specific section or line.
Key required fields: prebindSanctionCheckComplete.
claimsAgreementParty is a per-line attribute — supply it on each entry in quoteRequest.lines[], not here (XFI only exposes it at the policy-line level).
Section/line attributes (premiumBasis, typeofClaimBasis, instalmentbasis, leaderPercent, etc.) are carried in quoteRequest — not repeated here.
The optional fon block carries FON-stage policy-activity attributes (CY LOB only). The optional surplusBroker block is required for US-origin risks.
Required. Confirms the pre-bind sanction check has been completed. Set to true before proceeding to bind. The submission will be rejected if this check has not been completed.
Example:true
Obligor contact reference — id only.
Show Child Parameters
Major peril classification — id only. Server-derived from the risk’s class; supply here to override the derivation.
Show Child Parameters
Territory of the risk — code only (e.g. { "code": "USA" }). Represents the location of the risk, not the regulatory location. When multiple locations exist, use the country with the highest concentration of risk properties. Raise a query to the underwriter if the territory is unclear.
Show Child Parameters
Type of RI basis — id only. Required for Assumed (RI) business. Leave blank for Direct business.
Show Child Parameters
Prior and pending date (ISO 8601 date string, e.g. ‘2025-01-01’). Required for CY LOB. Leave blank for all other LOBs.
Example:2026-01-01
Whether prior acts cover applies to this risk.
Example:true
Retroactive date (ISO 8601 date string). Only applicable when priorActs is true; leave blank when priorActs is false. Required for PV, CY and PL LOBs. Leave blank for all other LOBs.
Example:2026-01-01
Bind-time insured enrichment — occupation, mailing/issuance address, policyholder type, and TINs.
Required fields: occupationSource (id), occupation, mailingAddressCountry (code).
Conditional required: mailingAddressState (US/Canada); webSite (CY LOB); assetsUnderManagement + assetSize (FI LOB); taxIdSpain / taxIdPortugal / taxIdItaly / canadianBusinessNumber (where insured has exposure in those countries).
Show Child Parameters
Surplus lines and sub-producer details. Required when risk premium originates from the United States.
Required fields: typeOfAdmitted (id, set to Surplus), surplusLinesBroker (id), brokerLicense, producerHomeState (code).
Additionally required when producerHomeState is New Jersey: slaNumber.
Show Child Parameters
Tail effective date at policy-activity level (ISO 8601 date string). Leave blank unless a tail period applies to this risk.
Example:2026-01-01
FON (Final Offer & Negotiation) policy-activity attributes. CY LOB only.
Required FON fields: fonDate (date), jurisdictionCountry (code), riskRegulatoryLocation (code).
Conditional required: jurisdictionState (code) for US risks.
The regulatory risk location is found in the Fiscal & Regulatory section of the slip — this represents where the regulator deems the risk to be situated, NOT the territory field.
Show Child Parameters
RI program associations. Supply when the policy is part of one or more RI program structures.
Show Child Parameters
Peer review sign-off for the bind.
Show Child Parameters
GlobalSubmissionResponse
objectMinimal response returned after the base Step Function completes.
Correlation id for tracing the background full + quote executions in logs
Example:9b3f7c1c-1f0a-4e2d-9d7c-2e3a8b4c6d2e
Policy number produced by the base submission step
Example:Q0038456
Policy key produced by the base submission step, propagated to the async steps
Example:20894
Policy activity key produced by the base submission step
Example:45632
ACCEPTED means the full step is running in background; FAILED means the base step failed
Allowed values:ACCEPTEDFAILED
Example:ACCEPTED
Human-readable message
Example:Base submission succeeded. The full step is running asynchronously.