Documentation Index
Fetch the complete documentation index at: https://mintlify.com/markzuckerbergas/gbmplus-api-python/llms.txt
Use this file to discover all available pages before exploring further.
gbm.transfers exposes a single method for moving funds between GBM+ investment strategies. Access it as gbm.transfers on any GBMPlusAPI instance.
Transfers use
account_id (returned by getAccounts()), not legacy_contract_id. See the Accounts reference for details on the difference between these two identifiers.transfer(amount, origin_account_id, target_account_id)
POST https://api.gbm.com/v1/contracts/{main_contract_id}/accounts/{origin_account_id}/transfers. The main_contract_id is resolved automatically from the session established at GBMPlusAPI initialisation.
The amount in MXN pesos to transfer from the origin strategy to the target strategy, e.g.
500 for $500 MXN.The
account_id of the source strategy. Retrieve this from gbm.accounts.getAccounts() — do not use legacy_contract_id.The
account_id of the destination strategy. Must belong to the same GBM+ contract as the origin.transfer_id that can be used with gbm.accounts.getStateOfTransfer() to poll the transfer status.
Example:
For a complete walkthrough of funding a strategy via transfer, see Transfer Funds. For the
account_id vs legacy_contract_id distinction, see the Accounts reference.