Distressed recovery
Integrate approved recovery fund, acquisition, auction, RFQ, refund, and claim workflows.
Distressed recovery is a controlled lifecycle for eligible participants, not a permissionless market or general exchange API. The documented acquisition, auction, and RFQ adapters are available to approved Developer Preview applications with the exact current role and scope.
Supported journey
| Stage | Canonical surfaces and workflow examples |
|---|---|
| Discover | Recovery funds, positions, approvals, subscriptions, holdings, cash receipts |
| Acquire | role.asset_manager.distressedRecoveryAcquisitionV3Bid |
| Bid at auction | role.lender.distressedRecoveryFundV3AuctionBid |
| Place or replace RFQ bid | distressedRecoveryFundV3RfqPlaceBid, distressedRecoveryFundV3RfqReplaceBid |
| Cancel, finalize, or refund | RfqCancelBid, RfqFinalize, RfqClaimRefund role workflows |
| Reconcile | GET /v1/liquidation-recovery, GraphQL recovery resources, signed events |
Safety rules
- Read participant eligibility and restricted-position approvals before preparing an action.
- Preserve fund, epoch, position, channel, bid, quote, token, amount, deadline, and authority context.
- Do not infer ownership or proceeds from an auction or RFQ event alone.
- A submitted or mined bid is not a finalized acquisition.
- Refund and claim workflows remain separate lifecycle states and may require their own authorized signer and canonical postcondition.
Event-driven operation
Store and deduplicate recovery events, then reconcile the affected fund, position, bid, refund, and cash-receipt resources. If canonical state is stale or does not match the expected lifecycle, fail closed and retain the request ID for support.
See Typed workflows, Canonical state, and Webhooks and events.