ReturnsDirect by LiquiDonate - Return and Refund Events
Version 1.0.0-beta
Outbound webhook event surface for ReturnsDirect by LiquiDonate. LiquiDonate POSTs return and refund status events to the webhook URL a retailer registers, so the retailer can update its own order management system. Every event is signed with HMAC-SHA256 over the raw request body using the shared secret LiquiDonate provisions for the shop, sent as lowercase hex in `X-Signature` alongside `X-Shop-Domain`. Verify with a timing-safe comparison before trusting the payload. This AsyncAPI was generated by the API Evangelist enrichment pipeline from the published webhook catalog and payload examples at https://docs-returns.liquidonate.com. LiquiDonate does not publish an AsyncAPI definition; every event name, field and example here is taken verbatim from that documentation.
View SpecView on GitHubReverse LogisticsReturns ManagementDonationsNon-ProfitRetailE-CommerceSustainabilityCircular EconomyShippingSupply ChainExcess InventoryCompanyAsyncAPIEventsWebhooks
Channels
returnsDirectEvents
The retailer-registered webhook endpoint LiquiDonate POSTs all return and refund status events to.
Messages
✉
return_pending
return.pending
A return request was created and is awaiting processing.
✉
return_pending_approval
return.pending_approval
A return is waiting on retailer or LiquiDonate approval.
✉
return_approved
return.approved
A return was approved.
✉
return_rejected
return.rejected
A return was rejected.
✉
return_cancelled
return.cancelled
A return was cancelled.
✉
refund_completed
refund.completed
A refund for an approved return completed.
✉
refund_flagged
refund.flagged
A refund was flagged for review rather than completing.
Servers
https
retailerWebhook
The retailer-operated HTTPS endpoint registered with LiquiDonate to receive events.
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.