policyKey returned by POST /submission/full
Example:21748
policyActivityKey returned by POST /submission/full
Example:33159
Adds quote (pricing and section) data to an existing policy activity — Step 2 of the submission lifecycle.
Pass the policyKey and policyActivityKey returned by POST /submission/full as query parameters.
sections array (at least one section with a valid agreement).
All id-based reference fields accept id only (e.g. summaryCurrency, solvencyIIClass). Currency fields (currency, limitCurrency, premiumCurrency, settlementCcy) accept code only.
The call typically completes within 20-40 seconds.
policyKey returned by POST /submission/full
Example:21748
policyActivityKey returned by POST /submission/full
Example:33159
Quote submission payload. Required: sections array. Reference fields use IdReference (id only) except currency fields which use CodeReference (code only).
Request body for POST /submission/quote — Step 3 of the submission lifecycle.
Required. Summary (reporting) currency — code only (e.g. { "code": "USD" }). Source: quote email, documentation, or submission email. If unavailable, escalate to WNS Team Lead → Mosaic Lead → Underwriter.
Required. Type of Cyber clause status — id only. Enter Cyber clause details per the quote document. Leave blank if not available at quote stage.
Required. US classification — id only. Source: fiscal and regulatory section of the slip. Select ‘Regulated’ or ‘Non-Regulated’ when risk originates from the United States. Select ‘Non-Regulated’ when the risk does not originate from the United States. Leave blank if details are not yet available at quote stage (do not query).
Unique Market Reference. Required. Source: risk details section of the UK slip. Leave blank if not yet available.
Example:B1234CYB2026001
Number of employees. Required for CY, FI and PL LOBs. Source: submission documentation or rater.
Example:250
Required. Insured annual revenue / turnover (numeric). Required for CY, FI, PL and Casualty LOBs. Source: booking sheet or Tyche rater. Update if a more accurate figure is available at quote stage.
Example:50000000
Number of Personally Identifiable Information (PII) records held by the insured. Required for CY LOB. Source: submission documentation.
Example:100000
Product template section to add.
Example:Directors and Officers
Bind probability expressed as a percentage string (e.g. ‘100%’). Indicates the likelihood the risk will proceed to bind. Supplied by the underwriter or front-end.
Example:100%
Major peril description (e.g. ‘Cyber Property’). Server-derived from the risk’s class and NAICS code; supply if known, otherwise leave blank for automatic derivation.
Example:Cyber Property
A single section within a quote submission. The front end sends at most two section objects: one for the main Agency policy (MSSL/MAIS etc.), and one for the Mosaic Asta Europe (MAE) policy when the risk has an EEA component. Each section carries a division.id that identifies which agency line it belongs to. Trident uses this to determine which syndicate lines (1609/2610 for the agency section; 5399/5431 for the MAE section) should be included via sectionIncluded.
A single agency policy line within a quote submission. Supply one element per underwriting agency line (one for the main Agency line; an additional one for the Mosaic Asta Europe agency line when the risk has an EEA component).
Front end supplies agency-line data only. Trident retrieves all XFI-created lines (agency + syndicate) via Get All Lines, identifies each by Division ID (Agency = front-end division.id; MAE = 7; 1609 = 3; 2610 = 12; 5399 = 6; 5431 = 13), and propagates most agency-line values to the syndicate lines (“Same as Agency Line”). Derived-only fields (originatingDivision, originatingOffice, global-risk cross-reference, inclusive-line) are computed by Trident and are not part of this payload.
Fields are grouped by stage: Submission → Quote → FON → Bind.
Quote created or updated successfully.
Response object containing cyber submission details including policy information, status, and reference keys
Current status of the policy
Allowed values:Quote PreparationPolicy UpdatedBoundDeclinedReferredQuote NTU
Example:Quote Preparation
Policy number assigned to the submission. Starts with ‘Q’ for quotes, ‘P’ for policies
Match pattern:^[QP]\d{7}$
Example:Q0038456
Business reference number for tracking purposes
Example:CYB-2026-001
Internal policy key identifier used for database references
Example:20894
Internal policy activity key identifier for tracking specific policy activities
Example:45632
Status of the current policy activity
Allowed values:ActiveCompletedPendingCancelledQuote NTU
Example:Active
Quote number assigned when the submission reaches quote stage.
Example:Q0021748
Declines a submission. Moves the policy to Submission Declined status.
Policy key
Policy activity key
Reason for declining submission
Policy declined successfully
Marks a quoted policy as Not Taken Up (NTU). Moves the policy from Quote to Quote NTU status, indicating the insured or broker chose not to proceed with the quoted terms.
Unique identifier of the policy to be marked as NTU
Example:20793
Unique identifier of the policy activity associated with the quote
Example:45632
Optional reason explaining why the quote was not taken up
Example:Insured found a more competitive quote elsewhere
Policy successfully marked as Quote NTU
Response object containing cyber submission details including policy information, status, and reference keys
Current status of the policy
Allowed values:Quote PreparationPolicy UpdatedBoundDeclinedReferredQuote NTU
Example:Quote Preparation
Policy number assigned to the submission. Starts with ‘Q’ for quotes, ‘P’ for policies
Match pattern:^[QP]\d{7}$
Example:Q0038456
Business reference number for tracking purposes
Example:CYB-2026-001
Internal policy key identifier used for database references
Example:20894
Internal policy activity key identifier for tracking specific policy activities
Example:45632
Status of the current policy activity
Allowed values:ActiveCompletedPendingCancelledQuote NTU
Example:Active
Quote number assigned when the submission reaches quote stage.
Example:Q0021748
Retrieves policy details from outbound-services-call API. PolicyNo is mandatory, xfiRef is optional.
Policy number (mandatory)
Example:22170
XFI reference (optional)
Example:XFI123
Policy details retrieved successfully
Response object containing full policy details retrieved from outbound-services-call API.
Unique identifier of the policy
Example:22170
Policy activity key identifier
Example:33650
Policy effective date
Example:2026-01-01
Policy expiry date
Example:2027-01-01
XFI quote reference
Name of the insured company
Example:Veritas Capital
Name of the producer
Example:ABC broking ltd
Email of the underwriter
Example:rajukumar.sah@dxc.com
Name of the underwriter
Example:Sah, Raju
Producer company name
Example:ABC broking ltd
Email of the producer
Example:chanchal.singh@dxc.com
Address details for insured or producer
Address details for insured or producer
Policy section containing deductions, coverages, and conditions
Producer company name
Example:ABC broking ltd
Retrieves a list of submissions filtered by source (e.g., MEA), class of business (e.g., cyber), and date range. Returns submission summary information including insured, broker, underwriter, dates, and status flags.
Class of business type (e.g., cyber)
Example:cyber
Start timestamp for filtering submissions (YYYY-MM-DDTHH:MM:SS)
Example:2024-01-01T00:00:00
End timestamp for filtering submissions (YYYY-MM-DDTHH:MM:SS)
Example:2024-12-31T23:59:59
Submissions list retrieved successfully