Policy number of the failed submission
Example:Q0038456
Administrative and development endpoints.
Starts a new state machine execution that resumes from the failed step (current_step on the status row). The original {base, full, quote, bind} payload is read back from the failed execution’s input via DescribeExecution; policyKey / policyActivityKey produced by the successful base step are taken from the status row.
Only allowed when overall_status = FAILED.
Policy number of the failed submission
Example:Q0038456
Identifies the calling system or channel that originated this request. Used for traceability and auditing across the platform.
Example:S01x
Identifier of the end user on whose behalf this request is made, recorded for audit trail purposes.
Example:jsmith
Retry accepted; new execution started.
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 the full step is running in background; FAILED means the base step failed
Allowed values:ACCEPTEDFAILED
Example:ACCEPTED
Human-readable message
Example:Base submission succeeded. The full step is running asynchronously.
Returns the per-step status (base / full / quote / bind) plus the attempt counters and last error messages for a submission. Updated by a background reconciler as the asynchronous steps complete.
Policy number returned by POST /policies/orchestrate
Example:Q0038456
Identifies the calling system or channel that originated this request. Used for traceability and auditing across the platform.
Example:S01x
Identifier of the end user on whose behalf this request is made, recorded for audit trail purposes.
Example:jsmith
Status row found.
Persisted per-step status for a global submission.
Example:9b3f7c1c-1f0a-4e2d-9d7c-2e3a8b4c6d2e
Example:Q0038456
Allowed values:PENDINGRUNNINGBASE_OKFULL_OKQUOTE_OKSUCCESSFAILED
Example:BASE_OK
Allowed values:BASEFULLQUOTEBINDDONE
Example:FULL
Example:arn:aws:states:us-east-2:123456789012:execution:TridentGlobalSubmission:fresh-9b3f7c1c-...
Example:20894
Example:45632
Allowed values:PENDINGSUCCESSFAILED
Example:SUCCESS
Example:1
Raw JSON output of the base step (audit)
Allowed values:PENDINGSUCCESSFAILED
Example:PENDING
Example:0
Allowed values:PENDINGSUCCESSFAILED
Example:PENDING
Example:0
Allowed values:PENDINGSUCCESSFAILED
Example:PENDING
Example:0
Example:2026-05-04T12:34:56.789Z
Example:2026-05-04T12:35:01.123Z
Extract submission data for use in other systems.
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. Accepted values: cyber, PL01, FI01.
Allowed values:cyberPL01FI01
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
Identifies the calling system or channel that originated this request. Used for traceability and auditing across the platform.
Example:S01x
Identifier of the end user on whose behalf this request is made, recorded for audit trail purposes.
Example:jsmith
Submissions list retrieved successfully