A participant on Zero Hash may enter into relationships with other participants. Current relationships that exist are:
operates_platform_for
This infers that one participant (the Platform Operator) operates a platform for another, upon which that other participant trades as a customer. An example is a broker participant operating a brokerage execution platform for another participant.
The Platform Operator can submit trades to Zero Hash where the customer participant is a counterparty. Read about the various ways you can submit a trade here.
The Platform Operator can also view the balances that have been allocated to their platform. There are various reports on the portal that offer this, and we also enable this via API.
GET /accounts
GET /accounts/net_delivery_obligations
GET /accounts/:account_id
GET /accounts/:account_id/run_history
GET /accounts/:account_id/movements
Note: This relationship is created at the same time as the customer_of_platform relationship.
customer_of_platform
This infers that one participant is a customer of another participant's platform, upon which the customer participant trades. An example is a participant being a customer on another participant's execution platform.
No access rights are obtained as part of this, however this relationship provides other participants access to your participant. See platform_operator_for access rights for more information.
Once added as a customer_of_platform, you will see new accounts into which you can allocate funds. The accounts will be labeled with the platform code. Any assets you allocate into the platform's account group will become visible to the platform and available for settling trades executed on that platform.
Note: This relationship is created at the same time as the platform_operator_for relationship.
submits_platform_withdrawals_for
This is an extension of the platform_operator_for relationship to enable withdrawal and deposit management.
The Platform Operator has the ability to submit withdrawals on behalf of a customer participant and interact with their withdrawal accounts over API (full spec here). Note: they can only submit withdrawals from their platform's account group.
POST /withdrawals/requests
GET /withdrawals/requests
GET /withdrawals/digital_asset_addresses
GET /withdrawals/fiat_accounts
The Platform Operator has the ability to get deposit information on behalf of a customer participant and generate new addresses over (full spec here).
GET /deposits/fiat_accounts
GET /deposits/digital_asset_addresses
POST /deposits/digital_asset_addresses
Note: This relationship is created at the same time as the platform_withdrawals_submitted_by relationship.
platform_withdrawals_submitted_by
This shows which other participants can submit withdrawals on behalf of your participant.
No access rights are obtained as part of this, however this relationship provides other participants access to your participant. See submits_platform_withdrawals_for access rights for more information.
This relationship is created at the same time as the submits_platform_withdrawals_for relationship.
submits_platform_transfers_for
This is an extension of the platform_operator_for relationship to enable account transfer management.
The Platform Operator has the ability to submit transfers on behalf of a customer participant over API (full spec here). Note: they can only submit transfers between their platform's account group.
POST /transfers
Note: This relationship is created at the same time as the platform_withdrawals_submitted_by relationship.
platform_transfers_submitted_by
This shows which other participants can submit transfers on behalf of your participant.
No access rights are obtained as part of this, however this relationship provides other participants access to your participant. See submits_platform_transfers_for access rights for more information.
This relationship is created at the same time as the submits_platform_transfers_for relationship.