MED_PROCESSING subscription for the intended owner. MED_PROCESSING is not one of the numeric values currently accepted by /v3/webhooks.
Subscription scopes
One source event can create separate USER and ACCOUNT deliveries. Each matching subscription receives its own
delivery_id. The callback exposes subscription_scope but does not expose the owner identifiers.
Events
A status-change event is not created when the status value is unchanged.
Envelope
Case status-change example
Case data
Case events contain:case_idtransaction_idroot_end_to_end_idstatusprevious_statusfor a status changerequested_amountblocked_amount_totalreturned_amount_totalcurrencyflow_typecreated_atupdated_atanalysis_deadlinemanual_refund_deadline
status values are:
CREATEDTRACKEDAWAITING_ANALYSISANALYZEDRETURN_PROCESSINGCOMPLETEDCANCELLEDFAILED
flow_type values are UNSPECIFIED, AUTOMATED, or MANUAL.
Infraction status-change example
Infraction data
Infraction events contain:case_idinfraction_iddict_infraction_idroot_end_to_end_idstatusprevious_statusfor a status changerequested_amountblocked_amountcurrencyanalysis_resultreceived_atsla_deadlineclosed_at
status values are:
RECEIVEDBLOCKING_PENDINGBLOCKEDANALYSIS_PENDINGCLOSED_AGREEDCLOSED_DISAGREEDCANCELLEDFAILED
analysis_result values are UNSPECIFIED, AGREED, or DISAGREED.
All MED amount fields are decimal strings. MED timestamps are JSON numbers containing Unix milliseconds. previous_status is omitted when it does not apply. Ignore unknown fields so additive payload changes do not break your receiver.
Ordering and idempotency
- Use
delivery_idas the delivery idempotency key. - The same
event_idsent to different subscriptions has differentdelivery_idvalues. - Deliveries are at least once and are not globally ordered.
- Use
resource_idandresource_versionto reject stale snapshots. - Do not derive business meaning by parsing
event_id.