Mid-term endorsement, confirmed
A 3-step recipe with QBE Insurance. We can help you get access.
Recipe · 3 steps
Mid-term endorsement, confirmed
with QBE Insurance
Endorse a policy, bind the change, then upload the endorsement schedule.
- Open the mid-term endorsement. Nothing is committed yet.
- Confirm the endorsement. Committing step, no idempotency key — never re-fire on a timeout. Replays the same x-master-ref-id sent on openEndorsement.
- Attach the endorsement schedule document to the policy.
What you'll need to have ready
- subscriptionKey: Approved Azure APIM subscription key.
- clientId: QBE-issued partner client id.
- clientSecret: QBE-issued partner client secret.
- partnerId: The calling QBE broker partner.
- trackingId: Your own tracing identifier.
- mockable: X-Mockable — true routes to QBE's WireMock scenarios.
- masterRefId: Correlation reference for this transaction. The SAME value must be sent on the opening endorse call and on the bind that confirms it.
- policyId: The in-force QBE policy to endorse.
- policy: Canonical policy document with policyHeader.policyTransactionInformation.transactionType ENDORSEMENT, the change effectiveDate, and the affected risks[] using r
- documentEffectiveDate: effectiveDate for the uploaded endorsement schedule.
- primaryFile: The endorsement schedule document payload.
For your developer
Arazzo workflow qbe:qbe-endorse-and-bind, 3 operations: Amend-an-existing-policy-endorsement → Bind-a-policy-to-save-change-after-endoresement-cancellation-or-renewal-has → Policy-Document-Upload-API. Specs on APIs.io.