Overview of the `fulfillment.failed` webhook

When a fulfillment.failed event is triggered, FastSpring sends a webhook payload containing details about the failed fulfillment actions. This webhook fires only when one or more fulfillment steps fail after a successful payment (for example, due to insufficient licenses in a pre-generated list).

This page provides:

A full sample payload showing a populated fulfillment.failed webhook
A detailed table listing every payload property, including name, type, and description
Notes on when this webhook is triggered and which fields appear based on Webhook Expansion

Webhook payload example

When a fulfillment.failed event is triggered, the webhook sends the following JSON payload:

{ 
   "product": "example-subscription-annual",
   "quote": "QUOT1234ABC5678XYZ",
   "fulfillment": "example-subscription-annual_license_1",
   "type": "license",
   "order": "aBCDE12fGH3iJkL4mNOpq",
   "reference": "ABC123456-7891-01112",
   "account": "abCdE1FGH2Hij3KLMnOpqR",
   "subscription": "-AbC1D2eFGH34ijklmnopQr",
   "reason": "Does not have available licenses."
}

Payload properties

All fields below are included in the fulfillment.failed webhook payload.

Name	Type	Description
Fulfillment Details
product	string	Product path of the item for which fulfillment failed
quote	string	Quote ID associated with the fulfillment
fulfillment	string	Fulfillment action ID for the action that failed
type	string	Fulfillment type such as `license`
order	string	Internal order ID of the associated order
reference	string	Customer-facing order reference ID of the associated order
account	string	FastSpring-generated customer account ID
subscription	string	Subscription ID associated with the fulfillment, when applicable
reason	string	Reason for the fulfillment failure, such as `Does not have available licenses`