Policy key
Policy activity key
Reason for declining submission
Declines a policy submission by invoking the decline action. This 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) by invoking the quoteNTU action. This moves the policy from ‘Quote’ status to ‘Quote NTU’ status, indicating the insured or broker has chosen 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
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
Retrieves submission data for a specific submission ID based on the class of business (cyber, pv, or enviro). Returns the submission details in a HashMap with the class of business as the key.
Unique submission identifier
Example:CY01-20251015-14
MEA submission found and returned successfully
Starts the TridentGlobalSubmission Step Function. The base step runs synchronously and its policyNo / policyKey / policyActivityKey are returned in the response. The full, quote, and bind steps continue in the background; poll /submission/global/{policyNo}/status for their outcome.
Processing Time: Base step 35-40 seconds (synchronous), full + quote + bind steps run asynchronously.
Flat payload covering the base, full, quote, and bind downstream submissions. Each section in sections carries an agreement object plus arrays of coverage, deduction, and codeSplit lines.
Flat, duplicate-free payload for the global submission endpoint. Fields enforced by the orchestrator’s own bean-validation (@NotBlank/@NotEmpty) plus the downstream /submission/full full-validation group are listed under required.
Required by the orchestrator for the Step Function execution name; not forwarded to the base/full policy node
Example:Veritas Capital
Required by the orchestrator; the producer is forwarded by id
Example:ENTERPRISE BROKERS kkarmark
Example:2024-01-01
Example:2025-01-01
Wrapped downstream as policy.product.description
Example:Cyber
Wrapped downstream as office.description
Example:Head Office Canada
Example:100
Wrapped downstream as underWriterDetails.description
Example:Desai, stavan
Serialized as insuredRevenueTurnover in the full payload
Example:0
Wrapped downstream as insuredDomicileCountry.description
Example:Australia
Wrapped downstream as insuredDomicileState.description
Example:New South Wales
Downstream FullCyberSubmissionRequest.periodTBA is regex-validated YES|NO
Allowed values:YESNO
Example:NO
Wrapped downstream as mosaicOccupation.id for base/full; sent as a plain string to the quote/bind steps
Example:198
Downstream submissionSanctionCheckComplete is regex-validated YES|NO
Allowed values:YESNO
Example:YES
Wrapped downstream as possibleClashIdentified.code (regex-validated YES|NO)
Allowed values:YESNO
Example:NO
Wrapped downstream as clashResponse.code
Example:[ "" ]
Wrapped downstream as isThirdPartyCapacityDeployed.id
Example:2
Example:100
Wrapped downstream as stampUnderwriter.description
Example:Desai, stavan
Wrapped downstream as producingUnderwriter.description
Example:Desai, stavan
Serialized as revTurnover in the full payload
Example:10
Wrapped downstream as majorPeril.id for base/full; sent as a plain string to the quote/bind steps
Example:11
Example:B1234567890
One quote section. coverage, deduction, codeSplit are arrays so a section may carry multiple lines.
Example:Directors and Officers
Example:100%
Territory sent ONLY to the bind step (distinct from the shared territory)
Example:USA
Example:Test Obligor
Example:true
Code split information
Base step succeeded; full, quote, and bind are running asynchronously
Minimal 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 full + quote are running in background; FAILED means the base step failed
Allowed values:ACCEPTEDFAILED
Example:ACCEPTED
Human-readable message
Example:Base submission succeeded. Full, quote and bind steps are running asynchronously.