Policy cancellation
A 3-step recipe with QBE Insurance. We can help you get access.
Recipe · 3 steps
Policy cancellation
with QBE Insurance
Cancel a policy, bind the cancellation, then upload the cancellation schedule.
- Open the cancellation. Nothing is committed yet.
- Confirm the cancellation. Committing step, no idempotency key — resolve a timeout by reading state or contacting QBE, never by re-firing.
- Attach the cancellation 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 replayed from the cancel call onto the bind that confirms it.
- policyId: The in-force QBE policy to cancel.
- policy: Canonical policy document with policyHeader.policyTransactionInformation.transactionType CANCEL, the cancellation effectiveDate, and policyHeader.cancelReasonCo
- documentEffectiveDate: effectiveDate for the uploaded cancellation schedule.
- primaryFile: The cancellation schedule document payload.
For your developer
Arazzo workflow qbe:qbe-cancel-policy, 3 operations: Cancel-an-existing-policy → Bind-a-policy-to-save-change-after-endoresement-cancellation-or-renewal-has → Policy-Document-Upload-API. Specs on APIs.io.