Trident APIs
The Trident APIs let you create and progress cyber insurance submissions through their full lifecycle and look up reference data used across the platform.
Authentication
All endpoints require an API key sent in the x-api-key header.
Conventions
- All requests and responses use
application/json. - Dates use ISO 8601 (
YYYY-MM-DD). - Lookup objects accept any one of
id,code, ordescription— supply whichever you have. When more than one is provided,idtakes precedence. - Errors follow a uniform shape (
code,message) and use standard HTTP status codes.
Field requirement levels
Every request field is one of three levels, derived from the XFI SOP Mandatory rules:
- Required — listed in the schema
requiredarray; the request is rejected if absent. - Conditional — required only when a stated condition holds (e.g. LOB, country of origin, new contact). The condition is described in the field and carried in the machine-readable
x-conditional-requiredextension; the field is not inrequired. - Optional — supply only if known.
Submission lifecycle
- Base —
POST /submission/basecreates a new DRAFT cyber submission and returnspolicyKeyandpolicyActivityKey. - Full —
POST /submission/full?policyKey={policyKey}&policyActivityKey={policyActivityKey}enriches the draft with underwriting and classification data. - Quote —
POST /submission/quote?policyKey={policyKey}&policyActivityKey={policyActivityKey}adds pricing and section data.
A single-call orchestration of the entire lifecycle (Base + Full → Quote → Bind) is also available via POST /submission/global.
- Server 1:https://trident-api.connecttrident.com
Generated server url
api_key (apiKey)
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