Trident Api’s WorkFlow Data -
Generated server url
An API key is a token that you provide when making API calls. Include the token in a header parameter called x-api-key.
Example: x-api-key: 123
Creates a new shell submission. This is the initial step in the submission lifecycle. Validated with the BasicValidation group: insured, producer, and policy are mandatory; inside policy, effectiveDate, expiryDate, product, and territory are mandatory. All other reference objects (majorPeril, directAssumed, typeOfBilling, division, office, mop, typeOfPlacementBespoke) are optional — but when present each must carry at least one of id / code / description (see the reference-object rule in the API description).
Shell cyber submission request. insured, producer, and policy are required. Other reference objects are optional but must carry at least one of id/code/description when present.
Base submission payload. Validated with the BasicValidation group: insured, producer, and policy are required. The remaining reference objects are optional, but each present one must satisfy the at-least-one-of id/code/description rule.
Required. Insured details; insureContacts.id identifies the insured contact downstream.
Required. Producer reference (send id or description).
Required. Policy node (dates + currency/product/territory references).
Optional. Major peril (typically description, e.g. Cyber Property).
Optional.
Optional.
Optional.
Optional.
Optional. Method of placement.
Optional.
Optional written line percentage
Example:100
Submission created
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
Adds the full-submission detail to a policy. Validated with the FullValidation group. The full-specific fields are REQUIRED: underWriterDetails, riskRegulatoryLoctn, insuredDomicileCountry, insuredDomicileState, uSClassification, lloydsIndustrialSector, mosaicOccupation, possibleClashIdentified, stampUnderwriter, producingUnderwriter. The scalars periodTBA and submissionSanctionCheckComplete (each YES/NO), insuredRevenueTurnover (≥ 0) and rev.-Turnover are also required. Each reference object present must carry at least one of id / code / description.
Policy key returned by the base step (omit to create a new policy)
Example:21355
Policy activity key returned by the base step
Example:32634
Full cyber submission request. Validated with the FullValidation group. The base parents (insured, producer, policy) are REQUIRED along with full-specific reference objects. Each reference object must carry at least one of id/code/description.
Full submission payload. Validated with the FullValidation group. The fields listed under required below are mandatory for this step. Every reference object present must satisfy the at-least-one-of rule.
Required. Underwriter (typically description).
Required.
Required.
Required.
Required. (Serialized JSON key uSClassification.)
Required.
Required.
Required. Its code must be YES or NO.
Optional.
Optional. (Serialized JSON key sBFClass.)
Optional.
Optional.
Optional.
Required.
Required.
Required. Must be YES or NO.
Allowed values:YESNO
Default:NO
Example:NO
Optional unique market reference
Example:B1234567890
Required. Must be YES or NO.
Allowed values:YESNO
Default:YES
Example:YES
Required. Must be ≥ 0.
>= 0
Example:0
Optional
Example:100
Required. Serialized JSON key rev.-Turnover (backed by Java field revTurnover).
Example:10
Full submission created
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
Creates a complete cyber Quote submission with comprehensive validation. This endpoint processes all submission Quote details including Agreement information, Coverage details, Deducation Details.
Processing Time: 40-60 seconds
Validation Rules:
agreementActivity(expecting agreementActivity as code),
agreementSection(expecting agreementSection as code),
100%Limit,
solvencyIIClass(expecting solvencyIIClass as code),
aggregateLimit,
premium,
limitOccurrence,
100%Limit,
limitAggregate,
ratedPremium(100%),
deduction(expecting deductionType as code),
deductionRate(expecting deductionBasis as code),
regulatoryCode(expecting regulatoryCode as code),
codeSplitPc,
gELR,
productTemplateSectionToAdd,
bindProbability(expecting bindprobability as code),
majorPeril,
uMR]
Optional policy ID for updating existing policies
Example:POL123456
Optional policy activity ID for specific policy activities
Example:ACT789012
Complete full cyber Quote submission request with all required and optional fields. This comprehensive request includes Agreement details, Coverage information, Deductions specifications, Codesplit details, and classification information.
List of sections in the quote
Product template section to add
Bind probability
Major peril description
Full submission created successfully - Submission processed and created with all details
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
Policy key for the submission to bind
Example:POL123456
Policy activity key for the submission to bind
Example:ACT789012
Complete cyber submission request
territory code for the bind, e.g., ‘USA’, ‘EU’, ‘APAC’
majorPeril code for the bind, e.g., ‘CYB’
mosaicOccupation code for the bind, e.g., ‘MOS001’
obligor description for the bind, e.g., ‘Test Obligor’
OK