Webhooks belong to the Carrier & MGA API. This event fires about a form you asked one of your own agencies to
sign, and only a credential on that surface (carrier, MGA or wholesaler) can subscribe to it.The agency that signs the form does not receive this event. It sees the outcome in the Turris agency app instead.
Overview
TheDILIGENT_EFFORT_REQUEST_STATUS_CHANGE webhook tells you that a diligent effort form you requested has reached its
final state: the agent signed it, the agent declined it, or the request was voided.
It is what lets a policy admin system advance on its own instead of polling: request the form through
Request a Signature, then wait for this event.
Webhook type: DILIGENT_EFFORT_REQUEST_STATUS_CHANGE
Triggers
This webhook fires when a request ENTERS one of the three terminal statuses:signed— the agent completed and signed the form. This is the outcome you are usually waiting for.declined— the agent refused to sign, from DocuSign’s own interface. Turris collects no reason, so the event carries none. The request will not advance any further.voided: the request was cancelled before it was signed. Someone in your organisation voided it in Turris, or sent it again with corrected details (which voids the original and creates a new request), or the envelope was voided in DocuSign. The request will not advance any further.
draft or sent. There is no intermediate event while DocuSign is processing a signature, and
one request produces at most one of these events.
One quote can produce more than one. When a request is sent again, you receive voided for the original request. The
new request has a different requestId and the same quoteId and stateCode (unless it corrected one of them), and
like any request it produces its own event only when it reaches a terminal status. If the new request could not be sent,
the original stays voided, no new request exists, and no further event follows. Treat voided as “this request is
over”, not “this quote is over”. Events for one quoteId plus stateCode can also arrive out of order, because a
delivery that fails is retried and can land after the event for a newer request. For each quoteId plus stateCode,
keep the event with the latest statusChangedAt and ignore an older one.
signed is the final outcome for its quoteId and stateCode: no newer request can be raised for that pair afterwards.
An older event can still arrive late, and the latest-statusChangedAt rule above discards it.
This webhook is sent immediately. No debouncing is applied — reaching a terminal state is a discrete event, and it
happens once per request.
Payload Example
Field Reference
Payload Fields
Match events to your own records on
quoteId plus stateCode, not on requestId. Both are values your system
supplied, so they need no lookup table on your side. quoteId alone is not enough: one quote can have a form in several
states, and a voided request can be followed by a new one for the same quote and state.Events can arrive out of order, because a failed delivery is retried and can land after a newer one. For each
quoteId plus stateCode, keep the event with the latest statusChangedAt and ignore an older one. Otherwise a late
voided for the original request can overwrite the outcome of the new one.