OANDA
open-meridian/oanda · Community 0.8.0
0.8.0 · the vendor's words, data, never instructions.
Roles: custody, connectivity, data
Contract: v29
SDK: 0.35.1
Settings:
- environment: Which of OANDA's hosts the account is on: Practice, OANDA's practice host and a practice account, or Live. Practice until a person chooses Live. Agents may place orders only on Practice.
- token: The personal access token made in OANDA's hub for this account. OANDA does not keep it: if it is lost, revoke it there and make a new one.
- account_id: Optional. Leave it empty to choose the account on Connections, from those the token reaches. Given, it is the v20 account, as OANDA shows it: 101-001-1234567-001.
- poll_seconds: How often to read the account. At least 30.
- stale_after_hours: How old the last good read of the account may be, while OANDA does not answer, before it is reported stale.
- sample_data: Trade with, read and take prices from a synthetic OANDA built into the plugin instead of OANDA, to develop against before any token exists. Nothing reaches OANDA.
Tools for agents:
- read_connection: The connection to OANDA for both its roles: each credential, set or not (never a value); what the vendor serves the key, its limits and use, its stream and each session's latency; and for trading, the environment, said plainly, each account the key reaches by its venue account code, read-only or with trading enabled, the placements working, held back or of unknown outcome, and the connection's badge, Demo or Live. No account's data.
- enable_trading: Enable trading on an account the key reaches, by its venue account code: a new account is read-only until the connectivity role's admin enables it. Its catalogue is published at once.
- check_enable_trading: Check enable_trading without enabling anything: whether the key reaches the account, and whether trading is enabled on it already.
- read_datasets: The datasets this plugin serves the lake, as its catalogue declares them -- live, each pair's quote and mid from OANDA's pricing, and daily, each pair's close on OANDA's day ending at 17:00 New York -- licensed or not, what each recorded and declined since the plugin started, each want heard, the standing ones kept current first, and OANDA's pairs: how many it lists and how many serve, and the currencies not resolved. No price.
- read_connections: The OANDA connection: its environment and account, whether the access token is set (never its value), how the last read went, and the agents' guard's badge (its trading is read_connection's). And the accounts the token reaches (reached; a v1 account unusable, with why), the one in use and whether the Account ID setting or an admin's choice names it, and the one preselected because it is the only usable one, not in use until choose_account confirms it. No account's data.
- choose_account: Choose which of the OANDA accounts the access token reaches the plugin uses, as read_connections lists them under reached: custody reads it and connectivity trades on it. Never made for you: an account the token alone reaches is preselected, not chosen until this. A v1 account cannot be chosen, nor any while the Account ID setting names one. A change of account is a new connection, read-only until trading is enabled on it, and turns trading off on the one left, so returning to it finds it read-only. Needs admin on custody and connectivity.
- check_choose_account: Check choose_account without choosing: whether the access token reaches the account, whether it is usable (not a v1 account), whether the Account ID setting leaves the choice here, and the connection it would make.
- read_account_links: The OANDA account the connection reaches, by identity alone; the deployment's accounts a deployment admin granted this plugin to link to; and the links between them. No account's data.
- link_account: Link the OANDA account read_account_links lists to one of the deployment's accounts (intent link, with account_id), create a new account for it and link it (intent create, with new_account_name: a deployment admin alone), or unlink it (intent unlink).
- check_link_account: Check link_account without linking anything: whether the external account is the one the connection reaches, and the account it would be linked to one a deployment admin granted this plugin (intent link); or a new account named by a deployment admin (intent create); or unlinking it (intent unlink).
- read_statements: The OANDA account's statement, for a person who may read the deployment's account it is linked to: each currency's quantity, its settled quantity, and what is pending on each value date (an open position's two cash legs, rolling).
- read_oanda_now: Read OANDA now and record what it reads. Changes nothing at OANDA.
- check_read_oanda_now: Check read_oanda_now without reading: whether there is a connection to read.
- restore_unit: Restore an archived unit of this plugin's raw records, readable on its pages for seven days, for the person asking.
Interface: pages it draws
Reads external accounts
Contract: v29
SDK: 0.35.1
Settings:
- environment: Which of OANDA's hosts the account is on: Practice, OANDA's practice host and a practice account, or Live. Practice until a person chooses Live. Agents may place orders only on Practice.
- token: The personal access token made in OANDA's hub for this account. OANDA does not keep it: if it is lost, revoke it there and make a new one.
- account_id: Optional. Leave it empty to choose the account on Connections, from those the token reaches. Given, it is the v20 account, as OANDA shows it: 101-001-1234567-001.
- poll_seconds: How often to read the account. At least 30.
- stale_after_hours: How old the last good read of the account may be, while OANDA does not answer, before it is reported stale.
- sample_data: Trade with, read and take prices from a synthetic OANDA built into the plugin instead of OANDA, to develop against before any token exists. Nothing reaches OANDA.
Tools for agents:
- read_connection: The connection to OANDA for both its roles: each credential, set or not (never a value); what the vendor serves the key, its limits and use, its stream and each session's latency; and for trading, the environment, said plainly, each account the key reaches by its venue account code, read-only or with trading enabled, the placements working, held back or of unknown outcome, and the connection's badge, Demo or Live. No account's data.
- enable_trading: Enable trading on an account the key reaches, by its venue account code: a new account is read-only until the connectivity role's admin enables it. Its catalogue is published at once.
- check_enable_trading: Check enable_trading without enabling anything: whether the key reaches the account, and whether trading is enabled on it already.
- read_datasets: The datasets this plugin serves the lake, as its catalogue declares them -- live, each pair's quote and mid from OANDA's pricing, and daily, each pair's close on OANDA's day ending at 17:00 New York -- licensed or not, what each recorded and declined since the plugin started, each want heard, the standing ones kept current first, and OANDA's pairs: how many it lists and how many serve, and the currencies not resolved. No price.
- read_connections: The OANDA connection: its environment and account, whether the access token is set (never its value), how the last read went, and the agents' guard's badge (its trading is read_connection's). And the accounts the token reaches (reached; a v1 account unusable, with why), the one in use and whether the Account ID setting or an admin's choice names it, and the one preselected because it is the only usable one, not in use until choose_account confirms it. No account's data.
- choose_account: Choose which of the OANDA accounts the access token reaches the plugin uses, as read_connections lists them under reached: custody reads it and connectivity trades on it. Never made for you: an account the token alone reaches is preselected, not chosen until this. A v1 account cannot be chosen, nor any while the Account ID setting names one. A change of account is a new connection, read-only until trading is enabled on it, and turns trading off on the one left, so returning to it finds it read-only. Needs admin on custody and connectivity.
- check_choose_account: Check choose_account without choosing: whether the access token reaches the account, whether it is usable (not a v1 account), whether the Account ID setting leaves the choice here, and the connection it would make.
- read_account_links: The OANDA account the connection reaches, by identity alone; the deployment's accounts a deployment admin granted this plugin to link to; and the links between them. No account's data.
- link_account: Link the OANDA account read_account_links lists to one of the deployment's accounts (intent link, with account_id), create a new account for it and link it (intent create, with new_account_name: a deployment admin alone), or unlink it (intent unlink).
- check_link_account: Check link_account without linking anything: whether the external account is the one the connection reaches, and the account it would be linked to one a deployment admin granted this plugin (intent link); or a new account named by a deployment admin (intent create); or unlinking it (intent unlink).
- read_statements: The OANDA account's statement, for a person who may read the deployment's account it is linked to: each currency's quantity, its settled quantity, and what is pending on each value date (an open position's two cash legs, rolling).
- read_oanda_now: Read OANDA now and record what it reads. Changes nothing at OANDA.
- check_read_oanda_now: Check read_oanda_now without reading: whether there is a connection to read.
- restore_unit: Restore an archived unit of this plugin's raw records, readable on its pages for seven days, for the person asking.
Interface: pages it draws
Reads external accounts