{
"transaction": {
"id": "lbtx_8d2f5a39b461",
"benefit_id": "lben_3e8a1c74d952",
"program_id": "lprg_3e8a1c74d952",
"member_id": "lmbr_91f6b2e84a37",
"earning_rule_id": "lern_6a2d9f41c783",
"type": "FULFILLMENT",
"status": "APPROVED",
"details": {
"reason": "Coffee Club / Order paid bonus",
"rejection": null,
"metadata": {
"event_id": "evt_7d2f5a39b461",
"earning_item_id": "lernei_8d2f5a39b461"
},
"result": {
"details": {
"material": {
"type": "PRODUCT",
"product": {
"id": "prod_7d2f5a39b461"
}
}
}
}
},
"created_at": "2026-09-09T10:15:43.091Z",
"updated_at": null,
"object": "benefit_transaction"
}
}Fulfillment
Event data sent for a Loyalty v2 FULFILLMENT transaction handled by Workflows
WEBHOOK
FULFILLMENT
{
"transaction": {
"id": "lbtx_8d2f5a39b461",
"benefit_id": "lben_3e8a1c74d952",
"program_id": "lprg_3e8a1c74d952",
"member_id": "lmbr_91f6b2e84a37",
"earning_rule_id": "lern_6a2d9f41c783",
"type": "FULFILLMENT",
"status": "APPROVED",
"details": {
"reason": "Coffee Club / Order paid bonus",
"rejection": null,
"metadata": {
"event_id": "evt_7d2f5a39b461",
"earning_item_id": "lernei_8d2f5a39b461"
},
"result": {
"details": {
"material": {
"type": "PRODUCT",
"product": {
"id": "prod_7d2f5a39b461"
}
}
}
}
},
"created_at": "2026-09-09T10:15:43.091Z",
"updated_at": null,
"object": "benefit_transaction"
}
}The
This event can trigger a workflow when Loyalty transaction is configured with the Benefit transactions group and the
FULFILLMENT event indicates that a Loyalty v2 benefit was fulfilled for a member.
This page documents only the event data nested under
data. See Introduction to webhooks for the shared webhook structure, and Workflows webhooks for the full Workflows webhook payload.FULFILLMENT transaction type. If the workflow reaches a Webhook callout action, Voucherify sends a webhook to the action’s target URL.
Workflows send this transaction in the data.trigger object. The example uses the APPROVED status. A workflow can filter the trigger by transaction status: APPROVED or REJECTED. The matched status is available in data.trigger.transaction.status; it does not create a separate event type.
Successful results nest the fulfillment effect under data.transaction.details.result.details.Body
application/json
Event data object schema for FULFILLMENT.
A Loyalty v2 benefit transaction with the FULFILLMENT type.
Show child attributes
Show child attributes
Response
Webhook accepted
Last modified on September 25, 2026