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, or description — supply whichever you have. When more than one is provided, id takes 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 required array; 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-required extension; the field is not in required.
• Optional — supply only if known.

Submission lifecycle

1. Base — POST /submission/base creates a new DRAFT cyber submission and returns policyKey and policyActivityKey.
2. Full — POST /submission/full?policyKey={policyKey}&policyActivityKey={policyActivityKey} enriches the draft with underwriting and classification data.
3. 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.