Transfers
Retrieve a transfer
PlannedA transfer's stage, timeline and candidate buyers. The cluster keeps its Synpute ID throughout; the new contract links back to the old one.
get/v1/transfers/{transfer_id}
transfer:readPath parameters
- transfer_idstringrequired
- Transfer ID e.g. trf_8Hc3
Response 200 · Transfer
- candidatesarray of objectrequired
- Vetted buyers offered the capacity
+Show propertiesHide properties
- buyerSynpute ID
- Candidate buyer
- statusstring
- Status
inviteddiligenceaccepteddeclined
- clusterSynpute IDrequired
- Cluster being transferred
- facilitySynpute IDrequired
- Facility
- idstringrequired
- Transfer ID
- new_contractSynpute IDrequired
- Contract with the new buyer, once signed
- objectstringrequired
- Object type
- previous_contractSynpute IDrequired
- Defaulted contract
- stagestringrequired
- Where it stands
noticecure_periodstep_inmarketingre_leasedcancelled- timelinearray of objectrequired
- Stage changes, oldest first
+Show propertiesHide properties
- atstring
- Date
- stagestring
- Stage
noticecure_periodstep_inmarketingre_leasedcancelled
- triggerstringrequired
- Trigger used
payment_defaultbuyer_insolvencycovenant_breachoperator_default
Errors
403404return the standard error shape.