Mutations
Active mutations use snake_case names and mostly return a success / data / error envelope. The auth, organization, passkey, and onboarding mutations that powered the old web dashboards are still in the schema but are @deprecated (dashboard sunset) — see the bottom of this page.
The canonical way to authenticate a programmatic client is the CLI signed-request scheme or a REST API key — not the deprecated password
loginflow. See Authentication.
Exchange Accounts
mutation {
create_exchange_account(exchange_account: {
exchange_name: "binance"
account_name: "My Binance"
trading_type: "spot"
api_key: "..."
api_secret: "..."
}) {
success
data { id exchange_name is_active }
}
}mutation { update_exchange_account(id: "exc_123", exchange_account: { account_name: "Renamed" }) { success data { id } } }
mutation { delete_exchange_account(id: "exc_123") { success } }
mutation { sync_exchange_account(id: "exc_123") { success data { id balance last_sync_at } } }
mutation { test_exchange_account(account: { exchange_name: "binance", api_key: "...", api_secret: "..." }) { success error } }Strategies
Copiers
Trades
Bulk & maintenance
Higher-volume and housekeeping operations for trade ingestion and the partition store:
bulk_create_trades(trades: [BulkTradeInput!]!)
Insert many trades
bulk_update_trades(trades: [TradeUpdateInput!]!)
Update many trades
bulk_delete_trades(ids: [String!]!)
Delete many trades
import_trades_from_csv(csvData, mappings)
Import trades from CSV
import_trades_from_exchange(exchangeAccountId, startDate, endDate)
Backfill from an exchange
archive_old_trades(cutoffDate)
Archive trades before a date
sync_trade_with_exchange(id)
Reconcile one trade against the exchange
recalculate_trade_metrics(tradeIds, dateRange)
Recompute analytics
optimize_partition(year, month) / rebuild_indexes
Partition maintenance
User Settings
Notifications
Withdrawals
API Keys
CLI Identity
Waitlist
Admin
Active admin mutations (require a system-admin identity, authorized per-resolver via requireAdmin; all write to the AuditLog). These back the tokenbot-admin CLI:
Deprecated (dashboard-era) mutations
Still resolvable for backward compatibility, but @deprecated (web dashboard sunset) and slated for removal in v2.0. The password/OAuth/passkey login flows below are legacy — new clients should authenticate with the CLI signed-request scheme or a REST API key:
Auth:
register,login,verify_2fa_code,refresh_token,logout,logout_all,google_auth,x_auth,apple_auth,telegram_auth,verify_email,forgot_password,reset_password,generate_2fa,enable_2fa,disable_2faUser:
change_email,confirm_email_change,change_password,login_with_telegram,login_with_discordOrganizations:
create_organization,update_organization,delete_organization,invite_member,update_member_role,remove_member,switch_organizationPasskeys:
generatePasskeyRegistrationChallenge,registerPasskey,generatePasskeyLoginChallenge,loginWithPasskey,deletePasskey,renamePasskeyOnboarding:
updateOnboardingStatus,completeOnboarding,resetOnboarding,trackOnboardingEventAdmin (legacy):
adminResetUserPassword,adminChangeUserEmail,adminResetUser2FA,adminDeactivateUser,adminReactivateUser,adminToggleSystemAdmin,adminEnableApiKey,adminDisableApiKeyCRUD seed data:
create_user_reward/update_user_reward/delete_user_reward,create_reward_type/update_reward_type/delete_reward_type,create_trade_pair/update_trade_pair/delete_trade_pair,create_supported_exchange/update_supported_exchange/delete_supported_exchange,create_notification/update_notification,create_user_setting
Last updated
Was this helpful?

