  Getting Started with SnapTrade     Introduction  Welcome to SnapTrade  This is intended to be one of the first documents you read when learning how to use the SnapTrade API and will answer many questions you might have while getting started  This document when read from top to bottom is also a guide for making your first connection  and will get you set up to start pulling account data and placing trades   If you want a quick definitions reference while reading  see  Terminology  https   docs snaptrade com docs terminology    If you are unsure whether to build as an individual user or as an app with many end users  see  SnapTrade Personal vs Commercial  https   docs snaptrade com docs personal vs commercial    For a focused reference on Commercial credentials  Personal API keys  and Personal OAuth  see  Authentication Methods  https   docs snaptrade com docs authentication methods    Please see the FAQ of each section  as any questions you might have should be answered there   If after reading this document you still have questions or need help  please do not hesitate to contact us through our  Discord  https   discord gg rkYWBxb8Qu    For a live demo  see the  Getting Started Demo  https   docs snaptrade com demo getting started            API Keys    image png    assets 250312 apikey png    Your  API key  consists of a  clientId  and  consumerKey   Please note that your  consumerKey  is sensitive information and should be kept secure at all times  This  API key  is used to make any requests to the SnapTrade API  and is the first thing required to get started       How to  Create a new API Key  When you are ready to get started with SnapTrade and want to start making requests to our API  you will need to create your free and paid  API keys   You may create only your free key if preferred   1  Create a SnapTrade account at the  SnapTrade Dashboard  https   dashboard snaptrade com home   2  Verify your email  You cannot create any  API Keys  until your account is verified   3  Generate your free  API Key  through the  SnapTrade Dashboard  https   dashboard snaptrade com api key   4   OPTIONAL  Add a payment method through the Settings   Billing page of the  SnapTrade Dashboard  https   dashboard snaptrade com settings billing   5   OPTIONAL  Upgrade to Pay as you Go through Settings   Billing page of the  SnapTrade Dashboard  https   dashboard snaptrade com settings billing   6   OPTIONAL  Generate your paid  API Key  through the  SnapTrade Dashboard  https   dashboard snaptrade com api key    After completing these steps  you will have two SnapTrade  API Keys      A free  API Key  that limits the number of concurrent connections    Optionally  a paid  API Key  that allows for unlimited connections   These two  API keys  are essentially the same in terms of functionality  and the core difference between them is that the free  API key  is limited in terms of the number of concurrent connections you can have  You can use these  API keys  to make requests to the SnapTrade API       How to  Make a request to the SnapTrade API  When you have an  API Key  and want to start using the SnapTrade API  you will need to use your  API Key  to make requests to the SnapTrade API   1  With your Free  API Key   enter your  clientId  and  consumerKey  into the corresponding fields of  api ApiStatus check   2  Press  Send    In the box below the  request  you should receive a response from the SnapTrade API  The  api ApiStatus check  endpoint is the most basic request you can make to the SnapTrade API   You can also make this request with any of the SnapTrade SDKs  While we recommend using an SDK  custom direct API integrations can generate signatures by following  Request Signatures  https   docs snaptrade com docs request signatures        SnapTrade SDKs      Language       SDK Link                     Python      https   pypi org project snaptrade python sdk    https   pypi org project snaptrade python sdk      TypeScript      https   www npmjs com package snaptrade typescript sdk    https   www npmjs com package snaptrade typescript sdk      Java      https   central sonatype com artifact com snaptrade snaptrade java sdk    https   central sonatype com artifact com snaptrade snaptrade java sdk      Ruby      https   rubygems org gems snaptrade    https   rubygems org gems snaptrade      C       https   nuget org packages SnapTrade Net    https   nuget org packages SnapTrade Net      PHP      https   packagist org packages konfig snaptrade php sdk    https   packagist org packages konfig snaptrade php sdk      Go      https   pkg go dev github com passiv snaptrade sdks sdks go    https   pkg go dev github com passiv snaptrade sdks sdks go          API Keys FAQ  https   docs snaptrade com docs faq faq api keys           Users    image png    assets 250312 apikey2users png   Your  API key  will be used to manage a set of SnapTrade  users   A SnapTrade  user  consists of a  userId  and a  userSecret   The  userSecret  is a randomly generated string and is sensitive information  It should be kept secure at all times   Typically if you have an application that manages end users  each end user of your application will get one SnapTrade  user  that will be used to manage that end user s  connections   This way  SnapTrade  users  will be one to one with the end users of your application       How to  Create a new SnapTrade User  When you have a working  API Key  and want to create a new  connection  for a  user   you will first need to register a SnapTrade  user    1  Using your API Key  create a request to the  api Authentication registerSnapTradeUser  endpoint  You will need to provide a unique SnapTrade  userId    This can be anything that is immutable  For this reason  it is recommended to NOT use email addresses for a SnapTrade  userId   2  The response you receive from the SnapTrade API will contain the  userId  you provided and the  userSecret  generated by SnapTrade  The  userSecret  is a randomly generated string and is sensitive information   You can list your created users by using the  api Authentication listSnapTradeUsers  endpoint  and you can delete created users by using the  api Authentication deleteSnapTradeUser  endpoint  If needed  you may reset a user s userSecret by using the  api Authentication resetSnapTradeUserSecret  endpoint  Now that you have one or more SnapTrade  users  under your  API Key   you are ready to create  connections  under these  users         Users FAQ  https   docs snaptrade com docs faq faq users           Connections    image png    assets 250312 users2connections png   Each  user  under your SnapTrade API key will be used to create and manage  connections  associated with that user  Each connection is associated one to one with a set of credentials to an institution      info Throughout these docs  the term  connection  is used to refer to a linked brokerage account           How to  Create a new connection for a user  When you have a SnapTrade user and want to get access to their account data and or place trades for an account  you will need to create a  connection  for that user   1  Generate a new redirectURI for the SnapTrade Connection Portal using  api Authentication loginSnapTradeUser  3  Open the generated link  Depending on your application  there are different ways to open this link  See  Methods to Integrate the Connection Portal into Your Application  https   docs snaptrade com docs implement connection portal    Once you have successfully completed the Connection Portal Flow  you should have an active connection to work with  and should have access to the accounts under that connection        Connections FAQ  https   docs snaptrade com docs faq faq connections           Accounts    image png    assets 250312 connections2accounts png   When you create a  connection   SnapTrade will automatically sync all  accounts  under the set of credentials to the brokerage  For example  if you made a new  connection  to Questrade  a Canadian brokerage  and that  connection  had a TFSA  an RRSP and an FHSA account under those credentials  SnapTrade would make all these  accounts  accessible over the SnapTrade API   Once you have a connected  account   you are ready to move on to pulling account data  and placing trades for that account       How to  Get positions for an account  When you have at least one connected  account  and want to start making use of the  positions   you will first need to get the  accountId    1  You can find the  accountId  anywhere over the API where the  account  object is returned  In this example  call  api Connections listBrokerageAuthorizations  to list the user s connections  then call  api Connections listBrokerageAuthorizationAccounts  for the relevant connection to get the  accountId  of the account you wish to pull  positions  for  2  With the  accountId   call  api AccountInformation getUserAccountPositions   This will return a list of positions in the specified account   Once you have  positions  returned  you re able to make use of the data in analysis  monitoring  or another use case you might be interested in  Other core endpoints for retrieving account information include  api AccountInformation getUserAccountBalance  and  api AccountInformation getUserAccountOrders        How to  Place a checked trade for an account  When you have at least one connected  account  and want to place a trade in the account  you will need to follow these steps to place a checked order  Note that you may also place an order without checking it   1  You need to get the  universalSymbolId  for the instrument that you wish to place an order for  You can find this using  api Trading getUserAccountQuotes   2  Validate the order with  api Trading getOrderImpact   This is a safe way to check the impact that the trade will have on the account if it is executed  and this is recommended to show on a screen to your user to have them confirm the order  Save the  tradeId  returned by this endpoint  it will be used in the next step  This  tradeId  will expire after a few minutes  3  Using the  tradeId  returned from  api Trading getOrderImpact   place the checked order using  api Trading placeOrder   This will place the order at the brokerage for the account  and return the response given by the broker   The order will now show over the  api AccountInformation getUserAccountOrders  endpoint  If it does not  you may need to trigger a refresh for the connection using  api Connections refreshBrokerageAuthorization         Accounts FAQ  https   docs snaptrade com docs faq faq account information          image png    assets 250312 model png      Next Steps    To get started with Webhooks  see  Webhooks  https   docs snaptrade com docs webhooks    To get started with implementing the SnapTrade Connection Portal  see  Methods to Integrate the Connection Portal into Your Application  https   docs snaptrade com docs implement connection portal    To let your users access their data through AI assistants like Claude and ChatGPT  see  SnapTrade MCP Server  https   docs snaptrade com docs mcp server  

Getting Started with SnapTrade

  Authentication Methods  We currently support three authentication methods  Choose the method based on whether the caller is a Commercial app acting for its own end users  or a Personal user managing their own brokerage accounts through their SnapTrade account      info The current SDKs and parts of the API reference still describe   Commercial   authentication  Updates to the API reference and SDKs will follow shortly  Until then  use the rules below as the source of truth for which credentials to send   If you d like to try early SDK support  you can use the TypeScript SDK  11 0 0 canary 0  or Python SDK  12 0 0rc0   These are early design explorations  and feedback is very welcome          Quick Comparison    Method   Best for   Credentials used   User identity                               Commercial app authentication   Apps managing many end users    clientId    consumerKey    userId    userSecret    The  userId  and  userSecret  identify one SnapTrade user under the Commercial app     Personal API key authentication   SnapTrade Personal accounts using signed API requests for connected brokerage accounts    clientId    consumerKey    The Personal API key identifies the account owner     Personal OAuth authentication   Apps or connectors where the account owner signs in with their SnapTrade Personal account   OAuth access token   The Bearer token identifies the account owner    For a broader product model comparison  see  SnapTrade Personal vs Commercial  https   docs snaptrade com docs personal vs commercial       Commercial App Authentication  Use Commercial app authentication when you are building an application that manages brokerage connections for your own end users   This is the existing Commercial flow   1  Your backend stores the Commercial  clientId  and  consumerKey   2  Your backend creates one SnapTrade user per end user with  api Authentication registerSnapTradeUser   3  We return a  userId  and  userSecret  for that SnapTrade user  4  Your backend uses  clientId    consumerKey    userId   and  userSecret  when making user scoped API requests   The  consumerKey  is never sent directly to us  It is used to generate the request  Signature  header  Direct API requests using this method include      clientId  as a query parameter     timestamp  as a query parameter     Signature  as a request header     userId  and  userSecret  as query parameters for user scoped endpoints   Example request shape      http GET  api v1 accounts clientId  client id  timestamp  unix timestamp  userId  user id  userSecret  user secret  Signature   signature       Commercial apps should keep the  consumerKey  and each user s  userSecret  on a secure backend  Do not expose them in browser or mobile clients   For signature generation details  see  Request Signatures  https   docs snaptrade com docs request signatures   For user registration and connection setup  see  Getting Started with SnapTrade  https   docs snaptrade com docs getting started       Personal API Key Authentication  Use Personal API key authentication when you are using a SnapTrade Personal account and need signed API requests for that account s connected brokerages   This method uses a Personal  clientId  and  consumerKey   but does not use a separate  userId  or  userSecret   The Personal API key already belongs to the SnapTrade account owner  so we resolve the user from the key   Direct API requests using this method include      clientId  as a query parameter     timestamp  as a query parameter     Signature  as a request header    No  userId     No  userSecret    Example request shape      http GET  api v1 accounts clientId  client id  timestamp  unix timestamp  Signature   signature          info Some user scoped endpoints may still show  userId  and  userSecret  as required in the API reference  For Personal API key authentication  omit those fields even if the API reference currently shows them as required       Do not call  api Authentication registerSnapTradeUser  for Personal API key authentication  That endpoint is for Commercial apps creating SnapTrade users for their own end users   For more context on Personal API keys  see  SnapTrade Personal vs Commercial  https   docs snaptrade com docs personal vs commercial   For signing direct API requests  see  Request Signatures  https   docs snaptrade com docs request signatures       Personal OAuth Authentication  Use Personal OAuth authentication when the account owner signs in with their SnapTrade Personal account and grants your app access to their brokerage accounts with an OAuth access token   With this method  API requests use the OAuth access token as a Bearer token  Do not send  clientId    consumerKey    userId   or  userSecret  in the API request   Direct API requests using this method include      Authorization  Bearer  access token   as a request header    No  clientId     No  consumerKey     No  userId     No  userSecret     No request  Signature  header   Example request shape      http GET  api v1 accounts Authorization  Bearer  access token          info The API reference may still show API key fields   userId   or  userSecret  for endpoints that support Personal OAuth  For Bearer token requests  omit those fields and send only the OAuth access token in the  Authorization  header       The Bearer token identifies the account owner and scopes what the caller can do  Store access tokens securely and treat them as sensitive credentials   Personal OAuth follows the OAuth 2 0 authorization code flow with PKCE  OAuth clients can discover our current OAuth metadata at  https   api snaptrade com  well known oauth authorization server   including the authorization  token  introspection  revocation  and client registration endpoints      Choosing a Method  Use Commercial app authentication if your backend owns the integration and maps many app users to SnapTrade users  This is the only method that requires your app to manage  userId  and  userSecret    Use Personal API key authentication if you are using a SnapTrade Personal account and are comfortable with signed API requests   Use Personal OAuth authentication if the caller should never handle a  consumerKey    userId   or  userSecret   or if the access should be delegated through user consent      Related     SnapTrade Personal vs Commercial  https   docs snaptrade com docs personal vs commercial     Getting Started with SnapTrade  https   docs snaptrade com docs getting started     Request Signatures  https   docs snaptrade com docs request signatures     SnapTrade MCP Server  https   docs snaptrade com docs mcp server  

Authentication Methods

  SnapTrade Personal vs Commercial  SnapTrade supports two primary customer experiences    Personal   and   Commercial    Both can use SnapTrade to connect brokerage accounts  retrieve account data  and  where enabled  place trades  The important difference is who owns the SnapTrade account and how users are represented   Use this guide to choose the right integration model before building authentication  user registration  connection management  billing  and support flows      info Personal and Commercial are customer experiences  not billing plan names  Billing plans such as Free  Pay as you go  and Custom control limits  pricing  and feature availability  A customer s Personal or Commercial experience controls how SnapTrade users  credentials  OAuth  and Connection Portal flows behave          Quick Comparison    Area   Personal   Commercial                         Intended user   An individual using SnapTrade for their own brokerage accounts   A company building an app for its own end users     SnapTrade account owner   The individual investor   The developer  company  or partner     End user model   The signed in Personal user is the SnapTrade user   Your app creates one SnapTrade  userId  and  userSecret  per end user     Authentication options   Personal OAuth  or Personal client ID and consumer key   Commercial client ID and consumer key     API authorization   OAuth Bearer token for Personal OAuth  or signed requests with a Personal consumer key   Signed requests using the Commercial consumer key     User registration   Do not call  api Authentication registerSnapTradeUser  for Personal OAuth   Call  api Authentication registerSnapTradeUser  before creating connections     Connection Portal   Opens for the Personal user s own brokerage connections   Opens for a specific SnapTrade user managed by your app     MCP server   Supported  the MCP server is designed for SnapTrade Personal users   Not used with Commercial developer API keys     Key lifecycle   Personal customers can create one Personal client ID and consumer key in the dashboard   Commercial customers start with a test key and can create production keys after KYC approval     Billing   Free   Connected users and usage under the Commercial customer agreement       Choose Personal When  Choose the Personal experience when the person using SnapTrade is connecting and managing their own brokerage accounts   Common Personal use cases include     An individual using the SnapTrade Dashboard directly    A CLI  desktop app  or AI assistant connector that lets the user sign in with their own SnapTrade account    Portfolio analysis and trading for the user s own accounts    Connection management for the user s own brokerages   Personal OAuth is the preferred pattern when your app should not handle SnapTrade API credentials directly  The user signs in with SnapTrade  your app receives OAuth tokens  and API calls are scoped to that Personal user   For Personal OAuth     Use authorization code with PKCE    Store OAuth tokens securely    Do not create a SnapTrade user with  api Authentication registerSnapTradeUser     Do not store or send a  userSecret     Omit  userId  and  userSecret  when opening the Connection Portal  the Bearer token identifies the Personal user    Treat the current  read  scope as account data and connection management  not trade placement or order modification   Personal client ID and consumer key authentication is available for Personal users who need signed request workflows  including trading with their own accounts where enabled  In that case  the user still represents themselves  Unlike a Commercial integration  your app should not create a separate SnapTrade user for them      Choose Commercial When  Choose the Commercial experience when you are building an application for your own end users and need SnapTrade as infrastructure behind your product   Common Commercial use cases include     A fintech app that lets many app users connect their brokerages    A portfolio management  tax  financial planning  trading  or analytics product    A backend service that needs to create  track  and support many SnapTrade users    Production integrations that need webhooks  billing  compliance review  and higher limits   Commercial integrations use a SnapTrade client ID and consumer key  Your backend signs requests with the consumer key and keeps that key secret   For each end user in your application   1  Create a stable SnapTrade  userId  with  api Authentication registerSnapTradeUser   2  Store the returned  userSecret  securely  3  Generate a Connection Portal link with  api Authentication loginSnapTradeUser   4  Send your end user through the Connection Portal  5  Use the  userId    userSecret   and account IDs to retrieve data or perform enabled trading workflows   Commercial  userId  values should be immutable identifiers from your system  Avoid email addresses because users can change emails and because user IDs may appear in logs  support workflows  or billing reconciliation      Credentials And Keys  Both experiences can involve a SnapTrade client ID and consumer key  but they are used differently     Personal client ID and consumer key      Belong to an individual Personal customer    Represent that individual s SnapTrade access    Do not imply that your app should create subordinate SnapTrade users    Are useful for local tools or advanced Personal workflows where signed request authentication is available     Commercial client ID and consumer key      Belong to a company or developer customer    Represent an integration that manages many SnapTrade users    Must be stored only on a backend or other secure server side environment    Are used to generate request signatures and validate webhook signatures   In the SnapTrade Dashboard  Commercial customers typically create a test key first  Production key creation requires KYC approval and a payment method  Personal customers are limited to one free Personal client ID and consumer key  which they can use for their own production use cases      Users And Connections  The biggest implementation difference is whether your app creates SnapTrade users       Personal  With Personal OAuth  the OAuth token identifies the SnapTrade user  Your app can call normal SnapTrade APIs  but user identity is inferred from the token  Do not call user registration endpoints or store a  userSecret    When opening the Connection Portal for a Personal OAuth user  generate the portal link without  userId  or  userSecret   SnapTrade resolves the Personal user s context from the Bearer token       Commercial  With Commercial client ID and consumer key authentication  your app owns user mapping  Each end user of your app should have a corresponding SnapTrade user   A typical mapping is       Your app user      SnapTrade userId   userSecret      connections      accounts      Create one SnapTrade user per end user  then create one or more brokerage connections under that user  When a brokerage login contains multiple brokerage accounts  those accounts appear under the same connection      Trading And Write Access  Feature availability depends on the customer  key  brokerage  account  and plan   Personal users can trade with their own accounts using SnapTrade client ID and consumer key authentication where trading is enabled for the account and brokerage   For Personal OAuth  the current  read  scope supports account data and connection management workflows  Trading and other write operations require SnapTrade client ID and consumer key authentication where enabled   For Commercial integrations  trading requires     A Commercial key with trading features enabled    A brokerage and account that support trading    A connection created with the appropriate connection type    Your application s own user confirmation and compliance flow before submitting orders      MCP And AI Connectors  The SnapTrade MCP server is a Personal experience  It lets AI assistants read a Personal user s connected brokerage data after the user signs in with SnapTrade OAuth and approves read access   Commercial developer API keys are not used with the hosted MCP server  If you are building a Commercial product that includes AI features  your backend should use your Commercial integration model and expose only the user facing AI behavior you intend to support      Billing And Limits  Personal versus Commercial determines the user model  Personal users are currently completely free  Commercial billing plans determine pricing  limits  and enabled features for Commercial customers   Commercial billing is usually based on connected users and usage under the customer s agreement  A connected user is an end user who has at least one completed brokerage connection or relevant sync activity during the billing period   Plan level settings can affect     Number of allowed connections    Whether data is real time or daily    Whether manual refreshes are enabled or billable    Access to recent orders  trading  and other paid features    Whether production keys can be created   For Commercial integrations  design your onboarding  usage tracking  and support workflows around the connected user model described in  Billing  https   docs snaptrade com docs billing   Personal users do not need to design around Commercial connected user billing      Implementation Checklist  Before building  decide     Is the person connecting accounts the SnapTrade customer  or is your company the SnapTrade customer    Will users sign in with SnapTrade OAuth  or will your backend sign API requests with a consumer key    Should your app call  api Authentication registerSnapTradeUser     Where will credentials  OAuth tokens  and user secrets be stored    Who owns support for reconnecting brokerages and removing connections    If you are building a Commercial integration  which billing plan controls limits  data freshness  and feature access   If the user owns the SnapTrade account  use the Personal model  If your app owns the integration and manages many end users  use the Commercial model      Related     Getting Started with SnapTrade  https   docs snaptrade com docs getting started     Authentication Methods  https   docs snaptrade com docs authentication methods     Terminology  https   docs snaptrade com docs terminology     SnapTrade MCP Server  https   docs snaptrade com docs mcp server     Billing  https   docs snaptrade com docs billing     Request Signatures  https   docs snaptrade com docs request signatures  

SnapTrade Personal vs Commercial

Connection Portal

  Trading with SnapTrade  SnapTrade supports trading workflows for stocks  ETFs  other equities  options  and crypto  The exact feature set depends on the connected brokerage or exchange  so you should always  verify support  https   support snaptrade com brokerages table v e7bbcbf9f272441593f93decde660687  for the account you are about to trade with          Soft Rate Limit       We recommend limiting trade requests to   1 trade per second per account   to maximize execution success      Trading Overview  Most trading integrations with SnapTrade follow the same high level flow   1  Create or upgrade a trading enabled connection  2  Choose the brokerage account that will place the order  3  Build the order payload for the asset class you want to trade  4  Validate the order details in your application  5  Submit the order to the brokerage or exchange  6  Monitor execution status   The sections below explain how that flow differs for equities  options  and crypto      Set Up Trading Access      Create a Trading Connection  By default  connections are created with read only permissions  To create a trading enabled connection  set the  connectionType  body parameter to  trade  when calling  api Authentication loginSnapTradeUser    If you want to request trading access when it is supported  but still allow the user to connect read only accounts elsewhere  use  connectionType trade if available  instead       Enable Trading for an Existing Connection  To enable trading for an existing read only connection  ask the user to re authorize access   1  Set the  reconnect  body parameter to the ID of the existing connection  2  Set  connectionType trade  when calling  api Authentication loginSnapTradeUser   3  Direct the user to the re authorization URL that SnapTrade returns      Stocks  ETFs  and Other Equities  Use the standard trading endpoints for single leg equity orders       Typical Equity Workflow  1  Identify the account that will place the order  2  Identify the instrument using its brokerage  symbol   This is the recommended identifier when placing orders  3  Build the order details        action    BUY  or  SELL        order type   for example  Market    Limit    Stop   or  StopLimit        time in force   for example  Day  or  GTC        units  for share quantity  or  notional value  when supported 4  Validate the order details in your application before submission  5  Submit the order with  api Trading placeForceOrder    For most use cases  it is better to validate the order in your own application and then place it directly with  api Trading placeForceOrder   If you need SnapTrade to simulate the order impact before submission  you can use  api Trading getOrderImpact  and then submit the returned  tradeId  with  api Trading placeOrder   but this is usually not the primary workflow we recommend       Extended Hours Equity Trading  Extended hours trading is brokerage specific and only available when both the account and the instrument support it   To request extended hours execution     Set  trading session  EXTENDED   in the order payload    Use a  LIMIT  order with an appropriate time in force    Expect brokerage specific restrictions  Many brokerages only allow  DAY  orders for extended hours trading  while some also allow  GTC       Options  SnapTrade supports both single leg option orders and multi leg option strategies  but support is narrower than it is for equities       Single Leg Option Orders  Single leg option orders use the same endpoint as multi leg option orders  but with a single leg   1  Build the order for  api Trading placeMlegOrder   providing only a single leg  2  Provide  instrument symbol  with an  OCC format  https   en wikipedia org wiki Option symbol OCC format   3  Use an option action such as  BUY TO OPEN    BUY TO CLOSE    SELL TO OPEN   or  SELL TO CLOSE   4  Set  units  to the number of option contracts  5  Validate the order details in your application and submit the order with  api Trading placeMlegOrder    This is the right workflow for straightforward option buys and sells where the order has only one leg       Multi Leg Option Strategies  For spreads  condors  and other multi leg strategies  use  api Trading placeMlegOrder    The multi leg payload lets you submit     an  order type    a  time in force    a  price effect  such as debit or credit   a  legs  array containing the option instruments  actions  and contract quantities  Because brokerages often report each leg separately  downstream order history can appear as multiple records for a single multi leg submission      Crypto  SnapTrade supports specialized crypto trading endpoints for some exchanges such as Kraken  Binance  and Coinbase   Crypto trading uses tradable asset pairs represented as  BASE QUOTE   The action determines the direction of the trade     On a  BUY   the base asset is what you are buying and the quote asset is what you are spending    On a  SELL   the base asset is what you are selling and the quote asset is what you are receiving       Typical Crypto Workflow  1  Use  api Trading searchCryptocurrencyPairInstruments  to find the tradable pairs for the connected account  2  If needed  filter by  base  or  quote  because exchanges can support different pairs and sometimes different tickers for the same asset  3  Use  api Trading getCryptocurrencyPairQuote  to retrieve a quote for the pair  Quote values are returned in units of the quote asset  4  Validate the order details in your application  5  Submit the order with  api Trading placeCryptoOrder    When placing a crypto order  set the  instrument symbol  to the trading pair and the  instrument type  to  CRYPTOCURRENCY PAIR   The  amount  is the quantity of the base asset to buy or sell   For most crypto integrations  validating the request in your own application is simpler than relying on the preview endpoint  If you need an exchange side preview   api Trading previewCryptoOrder  is available      json      account id      accountId        instrument          symbol    ETH EUR        type    CRYPTOCURRENCY PAIR          side    BUY      type    MARKET      amount    0 01      time in force    GTC      post only   false        In this example  the order buys  0 01  ETH with EUR      Brokerage Support and Reconciliation  Not every brokerage supports every trading workflow  Extended hours sessions  multi leg options  and crypto trading are all institution specific  Review the  SnapTrade Brokerage Support Matrix  https   support snaptrade com brokerages table v e7bbcbf9f272441593f93decde660687  before enabling a feature in production   After placing an order  we recommend you reconcile the latest state by pulling a list of recent orders with  api AccountInformation getUserAccountRecentOrders   

Trading with SnapTrade

  Filtering Accounts by Category  SnapTrade connections can return multiple account types from a single brokerage login  For example  a Robinhood or Fidelity connection may include an investment brokerage account alongside a line of credit or deposit  bank  account   If your integration only supports investment flows   trading  holdings  balances   you ll want to filter out the non investment accounts so they don t surface in your UI or trade logic      The  account category  Field  Every account returned by SnapTrade includes an  account category  field that normalizes the account type across brokerages     Value   Meaning                INVESTMENT    Brokerage   investment account  equities  options  crypto        DEPOSIT    Bank deposit account  checking  savings        LOC    Line of credit account  for example  loans or credit cards        null    Category could not be determined  brokerage did not return a recognizable type   Treat as an investment account so legitimate brokerage accounts are not accidentally hidden from trading and holdings flows     The field is returned from both  api Connections listBrokerageAuthorizationAccounts  and  api AccountInformation getUserAccountDetails   If a user has multiple connections  call  api Connections listBrokerageAuthorizations  first  then call  api Connections listBrokerageAuthorizationAccounts  for each connection      The  raw type  Field  Alongside  account category   every account also includes a  raw type  field  This is the unnormalized account type string as provided by the brokerage  for example   Margin    INDIVIDUAL    ROTH    TFSA    Values differ per brokerage and are not standardized by SnapTrade   Use  raw type  when you need finer grained distinctions than  account category  provides   for example  separating retirement accounts from taxable brokerage accounts within the  INVESTMENT  category  For high level filtering between investment and non investment accounts  prefer  account category       Filtering in Your Code  The examples below select a single connection for brevity  If a user has multiple connections  choose the connection whose accounts you want to filter before listing accounts for that connection       Node js   TypeScript     ts const   data  connections     await snaptrade connections listBrokerageAuthorizations     userId    userSecret          Select the connection whose accounts you want to filter  const connection   connections 0   const   data  accounts     await snaptrade connections listBrokerageAuthorizationAccounts     authorizationId  connection id     userId    userSecret       const accounts       await Promise all      connections        filter  connection     connection id         map  connection             snaptrade connections listBrokerageAuthorizationAccounts             authorizationId  connection id             userId            userSecret                           flatMap  response     response data    const investmentAccounts   accounts filter     a     a account category      INVESTMENT     a account category     null             Python     python connections   snaptrade connections list brokerage authorizations      user id user id      user secret user secret    body    Select the connection whose accounts you want to filter  connection   connections 0  accounts   snaptrade connections list brokerage authorization accounts      authorization id connection  id        user id user id      user secret user secret    body  accounts      for connection in connections      accounts extend          snaptrade connections list brokerage authorization accounts              authorization id connection  id                user id user id              user secret user secret            body        investment accounts         a for a in accounts     if a get  account category   in   INVESTMENT   None             cURL     bash   Replace  authorizationId  with an id returned by  authorizations  curl  https   api snaptrade com api v1 authorizations  authorizationId  accounts userId     userSecret            jq         select  account category     INVESTMENT  or  account category    null               See also     Account Data  https   docs snaptrade com docs account data     Trading with SnapTrade  https   docs snaptrade com docs trading with snaptrade  

Filtering Accounts by Category

  Best practices to serve real time data  SnapTrade offers the ability to get real time data on both Pay as you Go   Real time and Pay as you Go   Daily plans  Real time requests are enabled by default on all non custom plans  See  our pricing page  https   snaptrade com pricing  for more information on plans      Pay as you Go   Real time  The best practice for showing users accurate data on Pay as you Go   Real time is to update your user s state when they log in to your app  You can do this by making API calls to the resources you need  commonly   positions  https   docs snaptrade com reference Account 20Information AccountInformation getUserAccountPositions     options  https   docs snaptrade com reference Options Options listOptionHoldings     balances  https   docs snaptrade com reference Account 20Information AccountInformation getUserAccountBalance   Repeat this process every 10 minutes while the user remains active in your application      Pay as you Go   Daily  On Pay as you Go   Daily  SnapTrade returns Daily data  Daily data is cached and refreshed once a day  Exact refresh timing may vary by brokerage  To get real time data we recommend calling  the manual refresh endpoint  https   docs snaptrade com reference Connections Connections refreshBrokerageAuthorization  to update the data  SnapTrade will begin a sync and notify you via  ACCOUNT HOLDINGS UPDATED  https   docs snaptrade com docs webhooks webhooks account holdings updated  webhooks when each account has finished syncing  at which point you can call   positions  https   docs snaptrade com reference Account 20Information AccountInformation getUserAccountPositions     options  https   docs snaptrade com reference Options Options listOptionHoldings     balances  https   docs snaptrade com reference Account 20Information AccountInformation getUserAccountBalance  for each account  If you expect your users to want intraday updates  it is a good idea to give the option of a refresh button that lets the user refresh their data in the same way  Note that calls to the Refresh endpoint will incur additional charges according to your plan      Get notified when users place trades at their broker  If you need to know when a trade has been placed by a specific user  the recommendation is to poll the  Recent Orders endpoint  https   docs snaptrade com reference Account 20Information AccountInformation getUserAccountRecentOrders   only during market hours  This endpoint defaults to returning the last day of executed orders  Keep a copy of this list on your end  and check if a new order is present in the polling responses  To avoid SnapTrade and institution rate limits  we recommend polling at most once every 5 minutes per account  If faster trade detection is needed  please check out https   docs snaptrade com docs webhooks webhooks trade detection and contact support snaptrade com if you wish to purchase a subscription  or reach out on discord slack        Transactions Please see  our guide on Syncing and Data Freshness  https   docs snaptrade com docs syncing  for more information about transactions     Relevant Endpoints    List account positions  https   docs snaptrade com reference Account 20Information AccountInformation getUserAccountPositions    List account option positions  https   docs snaptrade com reference Options Options listOptionHoldings    List account balances  https   docs snaptrade com reference Account 20Information AccountInformation getUserAccountBalance    List account orders  all   https   docs snaptrade com reference Account 20Information AccountInformation getUserAccountOrders    List account recent orders  for polling   https   docs snaptrade com reference Account 20Information AccountInformation getUserAccountRecentOrders    Get account detail  total account value   https   docs snaptrade com reference Account 20Information AccountInformation getUserAccountDetails  

Best practices to serve real-time data

  Webhooks  The SnapTrade API can be configured to send you webhook notifications when certain events happen   To get started with webhooks  visit the webhook tab of the SnapTrade Dashboard to configure a webhook listener     Verifying Webhook Authenticity    Note  Webhook secrets are deprecated   You can verify the authenticity of any SnapTrade webhook by using the  Signature  header contained in the webhook headers  and comparing that to the expected signature generated using your   consumer key    Note that the consumer key is different from the webhook secret that is being deprecated   The  Signature  header contains an HMAC SHA256 hash of the request body  using your consumer key as the key   Here s an example implementation of a Flask webhook handler that verifies the authenticity of incoming webhooks      python from base64 import b64encode from hashlib import sha256 import datetime import hmac import json import os from flask import Flask  request  jsonify  app   Flask   name     CONSUMER KEY   os getenv  SNAPTRADE CONSUMER KEY     app route      methods   POST    def webhook listener          Extract the payload     payload   request get json          Extract the Signature header     signature   request headers get  Signature          Verify the signature     sig content   json dumps payload  separators             sort keys True      sig digest   hmac new CONSUMER KEY encode    sig content encode    sha256  digest       calculated signature   b64encode sig digest  decode        if calculated signature    signature          raise Exception  Signature verification failed               Prevent replay attacks by checking the timestamp and making sure it was sent recently     timestamp   datetime datetime fromisoformat payload  eventTimestamp        if  datetime datetime now datetime timezone utc    timestamp  total seconds     300          raise Exception  Payload is too old         print  Signature verified successfully           Log the received data     print  Received payload    payload         Respond with a success message     return jsonify      200  if   name         main         app run host  0 0 0 0   port 5123       Aside from signature verification     SnapTrade supports custom webhook request headers  which are useful if your webhook handler is protected by Cloudflare    SnapTrade does not support IP whitelisting at this time    Handling Undeliverable Webhooks  When your webhook handler responds to our requests with a status code that is not 200  201  202  or 204  we mark that webhook as undelivered in our system   We will attempt to resend an undeliverable webhook notification with an exponential backoff  starting at 30 minutes  until it is either delivered successfully  or 3 retry attempts have been made     Webhook Types  The different webhook event types are outlined below      USER REGISTERED  Sent when a new user is successfully registered through the   registerUser   endpoint   Example payload is below      json      webhookId    dbaee13a 1184 4677 9741 b6845e60ee3a      clientId    phjBdpKfpN      eventTimestamp    2022 05 31T11 16 54 658533 00 00      userId    qQYISR9xcmR8ZtVHNgg1lbYgSQcxafPqPW0ZbE0yaA6ham6n54      eventType    USER REGISTERED      webhookSecret    lgCQWztweEFcHvjdLhHc            USER DELETED  Sent when a user is successfully deleted through the   deleteUser   endpoint   Example payload is below      json       userId   TOD1ACWHxnO9cnpq9XgNmFaRwXRMRu2taaFPpvYi6ng3uD2UN9       clientId   phjBdpKfpN       eventType   USER DELETED       webhookId   dbaee13a 1184 4677 9741 b6845e60ee3a       webhookSecret   lgCQWztweEFcHvjdLhHc       eventTimestamp   2025 01 08T14 32 59 979214 00 00            CONNECTION ATTEMPTED  Sent when a user a user attempts to make a brokerage connection  will also report the result of the attempt   Example payload is below      json      webhookId    6594d898 7377 453b 989e 03545ebde8bf      clientId    kqLsLciREm      eventTimestamp    2022 05 31T11 17 17 804976 00 00      userId    TOD1ACWHxnO9cnpq9XgNmFaRwXRMRu2taaFPpvYi6ng3uD2UN9      eventType    CONNECTION ATTEMPTED      connectionAttemptedResult    SUCCESS      brokerageId    c8153291 0761 43a8 8ed0 4642103c2cb8      webhookSecret    PajFGRsWwxgckkOZwteW         Possible values for the  connectionAttemptedResult  field are      SUCCESS     AUTH EXPIRED     INVALID AUTH CODE     AUTH NOT IN PROGRESS     DIFFERENT ACCOUNT     UNCAUGHT ERROR     INVALID CREDENTIALS     INVALID MFA CODE     NO DATA      CONNECTION ADDED  Sent when a new brokerage connection is created using the SnapTrade connection portal   Example payload is below      json      webhookId    7467e5e4 4b59 4514 9d04 d05dbc10dea9      clientId    cJEQQgtDIb      eventTimestamp    2022 05 31T11 13 37 269120 00 00      userId    oWbLZ3OWsO3Nt8DKJnYxM32wLLD6h6SVj0ywkDmypUlkWkqsI5      eventType    CONNECTION ADDED      brokerageId    c8153291 0761 43a8 8ed0 4642103c2cb8      brokerageAuthorizationId    a0231bd2 9b77 4732 ba78 f9c6af6a1a62      webhookSecret    ZSDkaLCRJndeZGgeaJnV            CONNECTION DELETED  Sent when a user deletes an existing connection using the SnapTrade connection portal   Example payload is below      json      webhookId    85a63984 6fb6 45fb bc3b 18582a89ab3c      clientId    gxKWQEIXGS      eventTimestamp    2022 05 31T11 35 33 753881 00 00      userId    a053epCMsmII9goant5wdQH7CaT0M00HgQiRaxWnK0MncDUF2c      eventType    CONNECTION DELETED      brokerageId    c8153291 0761 43a8 8ed0 4642103c2cb8      brokerageAuthorizationId    a0231bd2 9b77 4732 ba78 f9c6af6a1a62      webhookSecret    lbTycRhXwzVRJPovdNSN            CONNECTION BROKEN  Sent when a user s connection is broken  also referred to as disabled  for some reason  usually an inability to handshake with the brokerage s API  To resolve this state  see  Fix Disabled Connections  https   docs snaptrade com docs fix broken connections    Example payload is below      json      webhookId    434d23af 5f89 44f8 9415 5029557e64c7      clientId    yLNANjmwau      eventTimestamp    2022 05 31T11 37 50 590720 00 00      userId    DbjLqtPsj6G1MlDLtZaps4YhtckD0jWOuLQjl6GPW4FmpUa8eo      eventType    CONNECTION BROKEN      webhookSecret    SCNsZYmJcuXRiznplDdL      brokerageAuthorizationId    dc90a844 367b 4120 8b56 21040bfa6525            CONNECTION FIXED  Sent when a broken  disabled  connection is fixed   Example payload is below      json      webhookId    ae73c055 2308 4de4 bf0e d828bbac8c91      clientId    BVmifPEScc      eventTimestamp    2022 05 31T11 52 26 803063 00 00      userId    EKDO7W7YSWEZkOZUN5v1iMGF7ipEmOGjc6bMEm89y6vCrtnebH      eventType    CONNECTION FIXED      webhookSecret    zNKlROkqSEXjXBxfTsAu      brokerageAuthorizationId    5e942e13 2b39 47b2 b524 858b9d9849ed            CONNECTION UPDATED  Sent when a brokerage connection is updated   Example payload is below      json      webhookId    57a293e4 f7eb 49ad 92e2 80ac16e01af7      clientId    IZtBuuKXEA      eventTimestamp    2022 05 31T11 53 09 437310 00 00      userId    sXQQcRdQEmGSMizpv45gBlBANBeCWgEn9uSmLlEpa1YsZ7oAW8      eventType    CONNECTION UPDATED      webhookSecret    oHdlCBoExKtosDtTLVDc      brokerageAuthorizationId    7ed55083 7128 46ff 9317 43cd788f43ff            CONNECTION FAILED  Sent when a user s attempt to connect to a brokerage has failed   Example payload is below      json      webhookId    57a293e4 f7eb 49ad 92e2 80ac16e01af7      clientId    IZtBuuKXEA      eventTimestamp    2022 05 31T11 53 09 437310 00 00      userId    sXQQcRdQEmGSMizpv45gBlBANBeCWgEn9uSmLlEpa1YsZ7oAW8      eventType    CONNECTION FAILED      webhookSecret    oHdlCBoExKtosDtTLVDc            NEW ACCOUNT AVAILABLE  Sent when a new account is detected through a brokerage connection   Example payload is below      json      webhookId    6fe03e8c 201a 4c3f 92d0 acb825fc89cf      clientId    SjWLDemQUF      eventTimestamp    2022 05 31T12 37 18 630476 00 00      userId    hmznAjmLezKPaSnLIiNQweSGsf7MIlEvm9dcTao3gwjgBtulLK      eventType    NEW ACCOUNT AVAILABLE      webhookSecret    HZRnYEhLPgwyUXitkJBd      accountId    ec20134b 72e7 4e72 9b4c 9c7ddd1c479c      brokerageAuthorizationId    795de4e6 260e 45b3 815b 8f601c4cf448            ACCOUNT TRANSACTIONS INITIAL UPDATE  Sent when we complete the initial transactions sync after a new account is connected  The duration needed for the first sync can vary by brokerage and by how many historical transactions the user has  but usually takes between 1 60 seconds   Example payload is below      json      webhookId    aa7a7d5a 4a12 40df a329 feedc738eee9      clientId    rmCZBUGAXP      eventTimestamp    2022 05 31T12 39 47 182403 00 00      userId    7jN22b2AWHMOqOeujjaiU5kKOM8iITt11ENcUMftx6LBg9GTn2      eventType    ACCOUNT TRANSACTIONS INITIAL UPDATE      webhookSecret    gQNuZIBwPYUVAsXvCfOA      accountId    d9f55a48 5dc6 4100 acee 24e5dfd8ec26      brokerageAuthorizationId    d28affae f918 4ecd 8128 e5438e861706            ACCOUNT TRANSACTIONS UPDATED  Sent when account transactions are incrementally updated  After the initial sync has already completed  account will be checked for new transactions daily  If new transactions are found they will be saved and this webhook will be sent  Only ACCOUNT TRANSACTIONS INITIAL UPDATE gets sent upon first connection   Example payload is below      json      webhookId    4eb13e1c 5778 44c2 968d 813d81cb73a1      clientId    JELZRJPqui      eventTimestamp    2022 05 31T12 40 05 944481 00 00      userId    4XTxw0mZhffRCdrgPHBG1VqdklkVJdEz5Uor0hq29hwPYlLS7s      eventType    ACCOUNT TRANSACTIONS UPDATED      webhookSecret    DDAVBuPPGgqwADXgbcOE      accountId    6e30be12 4ab0 4ec0 8d4d 0dfdce509e36      brokerageAuthorizationId    8105b33e 3dd6 4189 b93e 31ccaa9d3b69            ACCOUNT REMOVED  Sent when an account is removed from a connection   Example payload is below      json      webhookId    60b9ad5f 9e78 43b2 af5a 8ce8412b1cd6      clientId    PARTNERAPP      eventTimestamp    2024 05 31T12 40 05 944481 00 00      userId    4XTxw0mZhffRCdrgPHBG1VqdklkVJdEz5Uor0hq29hwPYlLS7s      eventType    ACCOUNT REMOVED      webhookSecret    DDAVBuPPGgqwADXgbcOE      accountId    6e30be12 4ab0 4ec0 8d4d 0dfdce509e36      brokerageAuthorizationId    8105b33e 3dd6 4189 b93e 31ccaa9d3b69            ACCOUNT HOLDINGS UPDATED  Gets sent when holdings for an account has been updated  Updated does not necessarily mean that the holdings have changed  instead it means that updating holdings with new data has been attempted  In the rare case that a holdings update fails  for example when a brokerage s API is down for maintenance   the webhook will still be sent and details on what failed will be included as part of the details field in the body   This webhook will be sent when we run our daily account syncs  as well as if a manual account refresh has been requested via  https   docs snaptrade com reference Connections Connections refreshBrokerageAuthorization  Account Holdings in this context refers to     Positions    Balances    Orders    Total Account Value    Account Detail  Historical transactions will be polled for  but will not fetch transactions from the current day  Example payload is below     json      userId    60b9ad5f 8e78 43b2 af5a 8ce8412b1cd6      clientId    PARTNERAPP      accountId    45a3g56a eef6 4904 a68e d3f90c3e07c5      eventType    ACCOUNT HOLDINGS UPDATED      webhookId    312a13f3 3929 46dd a70f ade6aaefc100      brokerageId    905872ac a7b1 4031 a31f 790cba1bfc94      webhookSecret    yfqvPlWrTFILBcjCERPh      eventTimestamp    2024 03 01T14 38 13 111991 00 00      brokerageAuthorizationId    6bb1ahb0 b8c8 4b59 8bf9 7841d7a89c63      details          total value      success   true   error   null         positions      success   true   error   null         balances      success   true   error   null         orders      success   true   error   null                 TRADE DETECTION  Gets sent seconds after a trade has been executed in a specific account  Requires an account specific subscription  Please contact support snaptrade com  or reach out on discord slack  for more information about pricing and setting up subscriptions  Only available on certain brokerages   Returns a list of orders placed  Example payload is below     json        userId    60b9ad5f 8e78 43b2 af5a 8ce8412b1cd6        details              orders                                    legs                                                    action    BUY TO OPEN                            leg id   null                           status    EXECUTED                            instrument                                  symbol    AAPL  261218C00240000                                figi code   null                               asset type    OPTION                                description    AAPL CALL 7 17 240                                exchange mic code    OPRA                                                      total quantity    1 000000000                            execution price    19 2000000000                            filled quantity    1 000000000                            canceled quantity   null                                                           status    EXECUTED                    order role   null                   order type    LIMIT                    stop price    0 0000000000                    limit price    19 2000000000                    time placed    2026 05 08T18 52 02 810000Z                    time executed    2026 05 08T18 52 02 848000Z                    time in force    DAY                    trailing stop   null                   price currency    USD                    execution price    19 2000000000                    brokerage order id    124912433123                    brokerage group order id   null                                     clientId    PARTNERAPP        webookId    6963bc1c 8bca 4896 8faa e84b82f8f7b2        accountId    ad4202bb eaf7 4c7c a176 e8406612b1ca        eventType    TRADE DETECTION        webhookId    763bc1cd 8aca 4896 8faa e84b82f8f7b2        brokerageId    02952334 1d52 436f ba74 f3e9a98ea635        webhookSecret    yfqvPlWrTFILBcjCERPh        eventTimestamp    2026 05 08T18 52 08 123974 00 00        brokerageAuthorizationId    6bb1ahb1 b8c8 4b59 8bf9 7841d7a89c63            TRADE UPDATE  Beta webhook that gets sent when the status of trade placed through SnapTrade changes  For example  will be sent if a trade gets cancelled  executed  partitally filled  etc  Please contact support snaptrade com  or reach out on discord slack  to try out this experimental webhook  Only trades placed through SnapTrade will be monitored for status updates   Returns a the current order detail in the webhook body  Example payload is below     json        userId    60b9ad5f 8e78 43b2 af5a 8ce8412b1cd6        details              orders                                    legs                                                    action    BUY TO OPEN                            leg id   null                           status    EXECUTED                            instrument                                  symbol    AAPL  261218C00240000                                figi code   null                               asset type    OPTION                                description    AAPL CALL 7 17 240                                exchange mic code    OPRA                                                      total quantity    1 000000000                            execution price    19 2000000000                            filled quantity    1 000000000                            canceled quantity   null                                                           status    EXECUTED                    order role   null                   order type    LIMIT                    stop price    0 0000000000                    limit price    19 2000000000                    time placed    2026 05 08T18 52 02 810000Z                    time executed    2026 05 08T18 52 02 848000Z                    time in force    DAY                    trailing stop   null                   price currency    USD                    execution price    19 2000000000                    brokerage order id    124912433123                    brokerage group order id   null                                     clientId    PARTNERAPP        webookId    6963bc1c 8bca 4896 8faa e84b82f8f7b2        accountId    ad4202bb eaf7 4c7c a176 e8406612b1ca        eventType    TRADE UPDATE        webhookId    763bc1cd 8aca 4896 8faa e84b82f8f7b2        brokerageId    02952334 1d52 436f ba74 f3e9a98ea635        webhookSecret    yfqvPlWrTFILBcjCERPh        eventTimestamp    2026 05 08T18 52 08 123974 00 00        brokerageAuthorizationId    6bb1ahb1 b8c8 4b59 8bf9 7841d7a89c63        

Webhooks

  Rate Limiting  The SnapTrade API uses rate limiting to protect against bursts of incoming traffic and help maximize stability  Sending too many requests in quick succession will trigger error responses with HTTP status code  429    There are two layers of rate limiting that may apply to your requests   1    Customer level rate limiting      a global limit across all requests from your  clientId   2    Account level rate limiting      a  per account  https   docs snaptrade com docs account data  limit on specific account data endpoints   A request must pass both layers  Even if you have remaining capacity at the customer level  you can still be throttled at the account level  and vice versa   When you exceed a rate limit  the API returns an HTTP status code  429  with a response body indicating how long to wait before retrying      json   detail   Request was throttled  Expected available in 7 seconds    status code  429  code   0000           Customer Level Rate Limiting  Every SnapTrade client is rate limited to   250 requests per minute   by default  This limit applies globally across all API endpoints and all accounts  If you need a higher limit  paid customers can  SnapTrade support  mailto support snaptrade com  to request a limit increase       Response Headers  The following headers are returned on every response to help you track your customer level usage     Header   Description                X RateLimit Limit    The maximum number of requests you can make per minute       X RateLimit Remaining    The number of requests remaining in the current rolling window       X RateLimit Reset    The number of seconds until the next minutely rate limit resets     These are rolling limits that look at the trailing 60 seconds      Account Level Rate Limiting  In addition to the customer level limit  the SnapTrade API enforces a   per account   rate limit on endpoints that fetch account data  This limit is   10 requests per minute per account   by default       Note    Account level rate limiting is only enforced for   Personal   users  Commercial users are subject to the customer level limit only  For more on the difference  see  SnapTrade Personal vs Commercial  https   docs snaptrade com docs personal vs commercial    Account level rate limiting is scoped to the combination of your  clientId  and the  accountId  in the request URL  This means     Different accounts have   separate   rate limit buckets  Exhausting the limit on one account does not affect requests to other accounts    Different endpoints for the   same account share   a single bucket  For example  fetching balances and positions for the same account both count toward that account s limit       Affected Endpoints  Account level rate limiting applies to the following endpoints      api AccountInformation getUserHoldings     api AccountInformation getUserAccountDetails     api AccountInformation getUserAccountBalance     api AccountInformation getAllAccountPositions     api AccountInformation getUserAccountOrders     api AccountInformation getUserAccountRecentOrders     api AccountInformation getAccountActivities     api AccountInformation getUserAccountOrderDetail     api Trading getUserAccountQuotes       Note    While the per account rate limit allows up to 10 requests per minute  these endpoints should not be polled at this frequency  See  API Polling Patterns  https   docs snaptrade com docs launching your application 3 api polling patterns  for recommended usage patterns       Response Headers  When account level rate limiting is active  the following additional headers are returned     Header   Description                X RateLimit Account Limit    The maximum number of requests allowed per minute for this account       X RateLimit Account Remaining    The number of requests remaining for this account in the current rolling window       X RateLimit Account Reset    The number of seconds until the next request slot opens up for this account  This value counts down as time passes  reflecting the actual time until the oldest request in the window expires     These are rolling limits that look at the trailing 60 seconds      How the Two Layers Interact  Every request to an account endpoint is checked against both rate limits  The stricter limit wins     Customer Level   Account Level   Result                   Remaining capacity   Remaining capacity     Allowed       Remaining capacity   Exhausted     429    account limit      Exhausted   Remaining capacity     429    customer limit      Exhausted   Exhausted     429    both limits     When you receive a  429   check both sets of response headers to determine which limit you hit  If  X RateLimit Remaining  is  0   you have hit the customer level limit  If  X RateLimit Account Remaining  is  0   you have hit the account level limit      Common Causes and Mitigations      Aggressive syncs    Syncing user portfolios all at once increases the chance of hitting both rate limit tiers  Space out data syncs over time  and rotate across accounts rather than polling a single account repeatedly      Polling a single account    Rapidly polling the same account for updates  e g   order status  will quickly exhaust the per account limit  Use webhooks where available  or poll at intervals of at least 15 seconds per account      Increased user signup volumes    A sudden influx of new users  e g   after announcing a new integration  can spike customer level usage  Space out onboarding requests over a period of time      Best Practices for Handling 429s  You should add logic to your integration to watch for  429  responses from the API and handle them with a retry mechanism       Check the  Reset  header    Use  X RateLimit Reset   customer level  or  X RateLimit Account Reset   account level   depending on which limit you hit  to determine exactly how long to wait before retrying      Use exponential backoff    If headers are unavailable or you prefer a general approach  retry with exponential backoff      Add jitter    Introduce randomness into your retry timing to prevent  thundering herd problems  https   en wikipedia org wiki Thundering herd problem       Spread requests across accounts    If you need to sync multiple accounts  round robin across them rather than exhausting one account s limit before moving to the next  

Rate Limiting

  Launching your Application  Before you launch to production with the SnapTrade API  you should conduct a pre production implementation review  This ensures you ll have a successful launch and provide a great end user experience   The goal of this review is to     Enhance both your experience as a SnapTrade user and your end users  app experience   Prevent and minimize common pitfalls   Understand and optimize your needs and use cases  while identifying potential product gaps   Ensure a smooth product launch     The Pre Launch Checklist      1  SnapTrade Compliance Policy  You have read the  SnapTrade Compliance Policy  https   snaptrade com compliance policy  and your application is in compliance       2  API polling patterns  You don t call the Holdings API more than 4 times per day per user in the background  or more frequently than once per end user login and at set intervals while the user is actively using your app   You don t call the activities  transactions  endpoint more than once per account every 24 hours for an account   If you run a daily job to pull data  you spread the calls out as much as possible over the period   If your app uses webhooks  you poll the API correctly  using the proper endpoint and payload data  in response to the specific webhook type received       3  User Onboarding  You should have a user onboarding flow that handles registering a SnapTrade user and storing the generated user secret   SnapTrade allows read only access or trading access for brokerage connections  Making the user explicitly decide as part of the authentication flow helps them understand the nature of the connection they re creating  and ensures a good user experience       4  Users can View and Delete their Connections  The ability to view and delete existing connections is critical to allow users to manage their authorizations  and to stay compliant with GDPR and privacy guidelines   The following endpoints have the information you need for this      api Connections listBrokerageAuthorizations     api Connections removeBrokerageAuthorization       5  Handle Disabled Connections  You have a system for detecting disabled end user brokerage connections  via webhook  and a defined re connection flow to fix broken connections  This includes at least one method of detection and one way to notify users  such as in app notifications or emails    See  How to Fix Broken Connections  https   docs snaptrade com docs fix broken connections       6  New Integrations  You have a strategy for handling newly released integrations  If you are making use of the  broker  parameter when calling  api Authentication loginSnapTradeUser   you will need to manually add any new brokerage integrations that are released  If you are not using this parameter  newly released integrations will appear automatically in the Connection Portal  You can call  api ReferenceData getPartnerInfo  to stay up to date  This returns the configuration for your Clint ID  including allowed brokerage integrations and data access       7  Rate limiting  You are aware of the general rate limit and have a way of gracefully handling rate limit 429 errors in your app  If you re using trading functionality  you re not executing trades faster than 1 trade per connected account per second   See  Ratelimiting  https   docs snaptrade com docs ratelimiting        8  Trading  If you re using trading functionality  you must have either clear user consent for automated trading or a trade preview flow that shows all expected fees and commissions  Users must also have the ability to opt out of SnapTrade functionality and delete their brokerage connection at any time  It s recommended to not execute trades faster than 1 trade per connected account per second   See  Trading with SnapTrade  https   docs snaptrade com docs trading with snaptrade        9  Webhooks  You have set your webhook listener URL in the  SnapTrade Dashboard  https   dashboard snaptrade com       Next Steps    Get your Production Keys through the  SnapTrade Dashboard  https   dashboard snaptrade com    Reach out to us at  support snaptrade com  mailto support snaptrade com  or over  Discord  https   discord gg UDwzZUuQ  

Launching your Application

  Trade Detection Subscriptions      Summary    Important behavior and integration details for SnapTrade  TRADE DETECTION  webhook subscriptions      Related docs     Best practices to serve real time data    realtime data    TRADE DETECTION webhook    webhooks webhooks trade detection    TRADE DETECTION  notifies partners when SnapTrade detects an executed order in a subscribed account  This feature is only supported for accounts where the brokerage supports realtime order updates  You can manage your subscriptions when logged in to the SnapTrade Dashboard at https   dashboard snaptrade com webhooks     Eligibility  Trade detection runs only when all of the following are true     The account has an active  TRADE DETECTION  subscription for a supported brokerage    The customer has a paid SnapTrade key and is in good standing in terms of billing    The underlying brokerage connection is enabled and can return realtime order data   Because disabled or broken connections cannot return new data  partners should also listen for  CONNECTION BROKEN  webhooks  When a connection breaks  prompt the user to fix it as soon as possible using the public reconnection guidance   Fix Broken Connections  https   docs snaptrade com docs fix broken connections    Brokerage availability can change as brokerage capabilities change  Do not assume every brokerage supports  TRADE DETECTION   and feel free to ask about specific brokerage support      Scheduling  Trade detection is currently scheduled only near regular market hours  weekdays from about  9 00 AM  to  4 30 PM America New York    This is the current scheduler behavior  not a contractual delivery SLA  Orders outside this window may not produce immediate  TRADE DETECTION  notifications      How To Interpret The Webhook  Use the order payload  not webhook delivery metadata  to determine when a trade executed      details orders    contains the detected order records     details orders   time executed  is the source of truth for when the order was executed     eventTimestamp  is when SnapTrade created the webhook event   For order execution timing  prefer  details orders   time executed  over  eventTimestamp  Brokerages usually make orders available over their API only a few seconds after execution  but can occasionally have a longer delay of a minute or two  SnapTrade has no control over these intermittent brokerage delays   Connection health is a separate signal  A  TRADE DETECTION  subscription on an account does not mean the connection is currently healthy  so partners should use connection webhooks such as  CONNECTION BROKEN  and  CONNECTION FIXED  to keep users  brokerage connections usable      Billing  Trade detection billing is seat based  One seat is one subscribed account for one month   For example  if a partner subscribes three accounts for trade detection in a billing month  that counts as three seats for that month  

Trade Detection Subscriptions

  How We Bill at SnapTrade  This document explains every component of SnapTrade s Commercial billing process so you know exactly what you re paying for  when you ll be invoiced  and how payments work   Personal users are currently completely free  Commercial customers may be billed based on connected users  API usage  platform fees  or monthly minimums depending on their agreement  If you are deciding which customer model applies to your integration  start with  SnapTrade Personal vs Commercial  https   docs snaptrade com docs personal vs commercial            Billing Cycle  SnapTrade bills Commercial customers on a   monthly   cycle  Each invoice covers usage from the 1st through the last day of the previous calendar month  Invoices are generated on the   1st of each month             What We Charge For  A Commercial monthly invoice can include up to four types of charges       1  Connected Users  Tiered Pricing   The primary component of a Commercial bill is based on the number of   unique users   who had an active or inactive brokerage connection during the billing period  A  user  is identified by the  user id  assigned when creating users in your application  For more details on user creation  see the  SnapTrade user creation documentation  https   docs snaptrade com docs getting started getting started users    By default  Commercial customers start with a single flat rate of    2 00 per connected user per month    As your business scales  you can negotiate volume based tiered pricing where additional users above certain thresholds are charged at progressively lower rates  Contact support if you re interested in negotiating bulk tiered pricing     Example of tiered pricing       Tier   User Range   Per User Fee                                         1      0   100      2 00            2      101   500    1 75            3      501          1 50           With 250 connected users in this example  the Commercial bill would be    100 users x  2 00    200 00   150 users x  1 75    262 50     Total   462 50      What counts as a billable user    A user is counted if they had at least one completed brokerage connection or  periodic sync event  https   docs snaptrade com docs syncing  during the billing period  Incomplete connections are not billed       2  Manual Refreshes  If your Commercial agreement with SnapTrade contains pricing for manual refreshes  they will be charged according to the following details   When your application triggers a manual data refresh  sync  for a user s account  each refresh is recorded as a billable event  The default rate is set per Commercial customer based on their agreement with SnapTrade  Manual Sync is available for Pay as you go Daily plans at    0 05 per sync    This feature remains disabled for free plans       3  Recent Orders API Calls  If your Commercial plan includes provisions for the   recentOrders  endpoint  each API call to this endpoint is billed at a per call rate defined in your agreement   Pay as You Go customers have this feature included at no extra charge although this feature may be subject to rate limits at higher volumes       4  Platform Fee   Monthly Minimum  Custom plans may include a fixed   platform fee   that is charged every month regardless of usage  This fee is independent of your user count or API call volume  On custom plans it is possible to bundle in a certain number of connected users with the Platform Fee   Custom plans may include a   monthly minimum fee    If your usage based charges  connected users   manual refreshes   recent orders calls  fall below this minimum  you will be charged the monthly minimum instead  The platform fee  if applicable  is added on top of the monthly minimum           Invoice Total  A Commercial invoice total is calculated as         Connected users charge  accounting for tiered pricing if applicable    Manual refresh charges  if applicable    Recent orders API call charges  if applicable                                              Usage subtotal  or monthly minimum if applicable  whichever is greater    Platform fee  if applicable                                              Subtotal   Sales Tax  if applicable                                              Invoice total              What Happens If an Invoice Goes Unpaid  SnapTrade takes the following steps for overdue Commercial invoices   1    Reminder emails   are sent on the 1st of each month to customers with any invoices past their due date  The email includes the total outstanding amount  your production API key slug  and the date your keys will be disabled if payment is not received   2    API key disablement   occurs automatically after the grace period expires  see Payment Terms table above   The default value for grace period is five  5  business days  When your keys are disabled       Your production API keys stop working       All outstanding unpaid invoices are marked uncollectible in our system but it is still possible to pay them       Invoicing continues so that charges are tracked  but new invoices generated while disabled are also generated in an uncollectible status   3    Automatic re enablement   is checked every hour  Your API keys are automatically restored once       All overdue invoices are paid or voided    and        At least one payment was made   after   the suspension occurred  to confirm the balance has been settled            Viewing Your Billing Details  Commercial customers can use the  SnapTrade Dashboard  https   dashboard snaptrade com settings billing  to view invoices  download PDFs  and manage payment methods           Questions   If you have questions about your Commercial bill or need to discuss your pricing  reach out to your SnapTrade account contact or email the billing address provided in your invoice communications  

How We Bill at SnapTrade

  SnapTrade MCP Server  SnapTrade offers a hosted  Model Context Protocol  https   modelcontextprotocol io   MCP  server that lets AI assistants like Claude and ChatGPT securely read a user s connected brokerage data through natural language prompts  Once a user adds SnapTrade as a connector  they can ask their assistant about their balances  positions  orders  and account activity in plain language   The MCP server is available at  https   mcp snaptrade com mcp       info The MCP server is   read only    It can retrieve account data and generate a link to connect a new brokerage  but it cannot place trades  move money  or change account settings  For programmatic access to the full SnapTrade API  including trading  see  Getting Started with SnapTrade  https   docs snaptrade com docs getting started           Before you begin  The SnapTrade MCP server is for   SnapTrade Personal   users   individuals who connect and manage their own brokerage accounts with SnapTrade  It is not used with SnapTrade developer  partner  API keys   To use the connector  you ll need a free SnapTrade Personal account  If you don t have one yet  sign up at the  SnapTrade Dashboard  https   dashboard snaptrade com signup  and link at least one brokerage account before adding the connector to your AI assistant   For a broader comparison of Personal and Commercial customer experiences  see  SnapTrade Personal vs Commercial  https   docs snaptrade com docs personal vs commercial       What you can do with it  With the SnapTrade connector enabled  an AI assistant can     List the brokerages a user is connected to and the accounts under each connection   Retrieve account details  balances  and buying power   Retrieve positions and holdings across accounts   Review orders  recent orders  and order details   Review historical account activity such as deposits  dividends  and fees   Look up reference data such as currencies  exchange rates  stock exchanges  and security types   Generate a one time link the user can open to connect a new brokerage     How it works  The MCP server is a thin protocol adapter in front of the SnapTrade Partner API  AI assistants speak MCP  SnapTrade exposes a REST API  The MCP server translates between the two and forwards each request to the same endpoints SnapTrade partners already use       AI assistant     SnapTrade MCP server     SnapTrade Partner API     User s brokerages      No new data surface is introduced   the connector exposes a curated  read only subset of existing SnapTrade endpoints      Authentication and security  The connector uses the OAuth 2 0 authorization code grant with PKCE  When a user adds the connector  their AI assistant registers itself automatically using  Dynamic Client Registration  RFC 7591   https   www rfc editor org rfc rfc7591   The user is then redirected to SnapTrade to log in and approve access  Tokens issued to the assistant are scoped to  read   and the MCP server validates every request using  token introspection  RFC 7662   https   www rfc editor org rfc rfc7662  against SnapTrade s authorization server      info The AI assistant never sees a user s SnapTrade  userId  or  userSecret   and never sees brokerage login credentials  It only receives a short lived  read scoped access token  SnapTrade resolves the user from that token       Clients can discover the connector s OAuth configuration at these endpoints      https   mcp snaptrade com  well known oauth protected resource mcp     https   api snaptrade com  well known oauth authorization server mcp   For details on what data the connector accesses and how it is handled  see the  SnapTrade Connector Privacy Notice  https   docs snaptrade com docs connector privacy   For SnapTrade s overall security posture  see  snaptrade com security  https   snaptrade com security       Set up the connector in Claude  1  In Claude  go to   Customize   Connectors    2  Click        then   Add custom connector    3  Enter the MCP server URL   https   mcp snaptrade com mcp   4  Claude redirects you to SnapTrade  Log in and approve   read   access to your account data  5  Review the consent screen  which lists the read only scope being granted  6  After you approve  you are returned to Claude and the SnapTrade tools become available      Set up the connector in ChatGPT  1  In ChatGPT  go to   Settings   Apps   Connectors   Advanced settings   and turn on   Developer mode    2  Go to   Settings   Connectors   and click   Create    3  Enter a name  for example   SnapTrade   and the MCP server URL   https   mcp snaptrade com mcp   4  Set the authentication method to   OAuth   and confirm you trust the application  5  Click   Create    then complete the OAuth login flow with SnapTrade and approve   read   access  6  After you approve  the SnapTrade tools become available in your chats     Note  ChatGPT Developer mode and custom connectors are available on ChatGPT for web  not the desktop app   complete this setup at  chatgpt com  https   chatgpt com      Note  Once the SnapTrade app is approved in the ChatGPT app directory  users can add it directly from the directory without enabling Developer mode      Example prompts  Once the connector is enabled  a user can ask their assistant questions like       What brokerages am I connected to through SnapTrade        Show me my current balances and positions across all my accounts        What were my last 10 orders across all my accounts        I d like to connect my Alpaca account      the assistant calls  request connection link  and hands the user a one time URL to open in their browser      Available tools  The connector exposes 18 tools  All are read only except  request connection link   which generates a connection link for the user to open     Connections       Connections listBrokerageAuthorizations    list the user s brokerage connections    Connections listBrokerageAuthorizationAccounts    list the accounts under a connection    Account information       AccountInformation getUserAccountDetails    account details  including institution name and total value    AccountInformation getUserAccountBalance    cash balances and buying power    AccountInformation getAllAccountPositions    positions and holdings for an account    AccountInformation getAccountBalanceHistory    historical account balances    AccountInformation getUserAccountOrdersV2    orders for an account    AccountInformation getUserAccountRecentOrdersV2    recent orders for an account    AccountInformation getUserAccountOrderDetailV2    details for a single order    AccountInformation getAccountActivities    historical account activity such as deposits  dividends  and fees    Reference data       ReferenceData listAllCurrencies    supported currencies    ReferenceData listAllCurrenciesRates    exchange rates for all supported currencies    ReferenceData getCurrencyExchangeRatePair    exchange rate for a specific currency pair    ReferenceData getSecurityTypes    supported security types    ReferenceData getStockExchanges    supported stock exchanges    ReferenceData getPartnerInfo    brokerages and data access available to the connector    Connection helpers       list supported brokerages    list the brokerages the user can connect    request connection link    generate a one time URL the user opens to connect a new brokerage  The link is single use and expires after 5 minutes  The assistant cannot complete the connection itself  only the user s browser session can   Every tool is annotated so AI clients and users can tell read operations from write operations  Read tools are marked  readOnlyHint  true  and  destructiveHint  false    request connection link  is marked  readOnlyHint  false  and  destructiveHint  true   All tools are marked  openWorldHint  true       Manage and revoke access  A user can revoke a connector s access at any time from the SnapTrade dashboard under   Settings   Connected apps    Revoking access immediately invalidates the assistant s token   This is separate from disconnecting a brokerage   revoking connector access removes the AI assistant s access to SnapTrade  but leaves the user s brokerage connections intact      Support    General support   support snaptrade com    Security vulnerability reports   security snaptrade com           Related     SnapTrade Connector Privacy Notice  https   docs snaptrade com docs connector privacy     Getting Started with SnapTrade  https   docs snaptrade com docs getting started     Brokerage Integrations  https   docs snaptrade com docs integrations     Terminology  https   docs snaptrade com docs terminology  

SnapTrade MCP Server

  SnapTrade Connector Privacy Notice  This notice explains how the SnapTrade MCP server  the  connector   handles data when you connect SnapTrade to an AI assistant such as Claude or ChatGPT  It supplements the  SnapTrade Privacy Policy  https   snaptrade com privacy policy   which governs SnapTrade s services overall and applies in full  SnapTrade is operated by Passiv Inc   The connector is   read only    it can retrieve your account data and generate a link to connect a new brokerage  but it cannot place trades  move money  or change account settings      What data the connector accesses  When your AI assistant calls a connector tool in response to your prompt  the connector retrieves the following categories of data from SnapTrade and returns them to your assistant       Connections     the list of brokerages you have connected through SnapTrade and connection metadata such as institution name and connection status      Account details     account type  institution name  total account value  and sync status      Balances     cash balances and buying power  including per currency balances      Positions and holdings     the securities held in your accounts  with quantities and market values      Orders     open  filled  cancelled  and pending orders  including order history and individual order details      Account activity     historical transactions such as deposits  withdrawals  dividends  fees  buys  and sells      Reference data     currencies  exchange rates  stock exchanges  and security types  This data is not specific to you   The connector accesses this data   on demand    only in direct response to a prompt you make through your AI assistant  It does not collect or retrieve data proactively      What the connector does not access    The connector never exposes your SnapTrade  userId  or  userSecret  to the AI assistant  These partner level identifiers are stripped from every request before it reaches the assistant    The connector never accesses your brokerage login credentials or passwords    The connector cannot place trades  transfer funds  or change account settings  Access is limited to read only scope      How the connector uses data  The connector is a thin protocol adapter  It uses the data it retrieves solely to fulfill the request you made through your AI assistant  passing the response back to the assistant that asked for it   SnapTrade does not use connector data for advertising or profiling  and does not use it to train AI models      Data storage and retention  The connector is stateless  It does not maintain its own long term store of your account data   each tool call retrieves data from the SnapTrade Partner API and returns it to your assistant   Retention of the underlying account data that SnapTrade holds is governed by the  SnapTrade Privacy Policy  https   snaptrade com privacy policy   OAuth access tokens issued to your AI assistant are short lived and scoped to  read   Operational logs may be retained for security  reliability  and troubleshooting in line with SnapTrade s standard practices      Third party sharing  When a connector tool returns data  that data is delivered to the AI provider you chose to use   Anthropic for Claude  or OpenAI for ChatGPT  How those providers handle the data is governed by their own privacy policies      Anthropic Privacy Policy  https   www anthropic com legal privacy     OpenAI Privacy Policy  https   openai com policies privacy policy    SnapTrade does not sell your personal data  For information on SnapTrade s service providers and other data sharing  see the  SnapTrade Privacy Policy  https   snaptrade com privacy policy       Data minimization  The connector is designed to access the minimum data needed to answer your prompts     It requests only  read  scope   it cannot write to your accounts    It exposes only a curated set of read only endpoints  not the full SnapTrade API    It returns data only in direct response to a prompt  Nothing is collected  just in case     Partner level identifiers and credentials are removed from every request before the AI assistant sees it      Revoking access  You can revoke a connector s access at any time from the SnapTrade dashboard under   Settings   Connected apps    Revoking access immediately invalidates the AI assistant s token  Revoking connector access does not disconnect your brokerages   your SnapTrade connections remain intact  See  SnapTrade MCP Server  https   docs snaptrade com docs mcp server  for more on managing access      Contact  For privacy or data questions  contact  support snaptrade com   For security vulnerability reports  contact  security snaptrade com   SnapTrade is operated by Passiv Inc           Related     SnapTrade Privacy Policy  https   snaptrade com privacy policy     SnapTrade Terms and Conditions  https   snaptrade com terms and conditions     SnapTrade Security  https   snaptrade com security     SnapTrade Application Compliance Policy  https   snaptrade com compliance policy     SnapTrade MCP Server  https   docs snaptrade com docs mcp server  

SnapTrade Connector Privacy Notice

  Terminology     API Keys API Keys consist of a client ID   clientId   and a consumer key   consumerKey    Aliases  app credentials  integration credentials  Learn more   Getting Started  API Keys  https   docs snaptrade com docs getting started getting started api keys    Authentication Methods  https   docs snaptrade com docs authentication methods    FAQ  API Keys  https   docs snaptrade com docs faq faq api keys      Personal Customer A free SnapTrade customer experience for individuals who connect and manage their own brokerage accounts  Personal users can use SnapTrade OAuth or a Personal client ID and consumer key   Learn more   SnapTrade Personal vs Commercial  https   docs snaptrade com docs personal vs commercial      Commercial Customer A SnapTrade customer experience for companies and developers building apps for their own end users  Commercial integrations use a client ID and consumer key  create SnapTrade users for app users  and manage connections under those users   Learn more   SnapTrade Personal vs Commercial  https   docs snaptrade com docs personal vs commercial      Client ID The public key for your SnapTrade API key  In direct API requests  it is sent as the  clientId  query parameter      Consumer Key The secret key for your SnapTrade API key  Use the consumer key when generating request signatures or validating webhook signatures  Aliases  client secret     SnapTrade User  A user record under your API key that represents one of your end users and authorizes access to that user s SnapTrade data  Aliases  connected user record  SnapTrade profile  Learn more   Getting Started  Users  https   docs snaptrade com docs getting started getting started users    FAQ  Users  https   docs snaptrade com docs faq faq users      Institution The financial provider a user connects through SnapTrade  such as a broker or exchange  Aliases  broker  brokerage  provider  integration  Learn more   Brokerage Integrations  https   docs snaptrade com docs integrations      Connection An authorized link between a SnapTrade user and one brokerage login that grants data access and optionally trading access  Aliases  brokerage authorization  linked brokerage  authorization  Learn more   Connections  https   docs snaptrade com docs connections    Getting Started  Connections  https   docs snaptrade com docs getting started getting started connections      Connection Portal The hosted SnapTrade UI flow your user completes to create  repair  or upgrade a connection  Aliases  connect flow  linking flow  auth portal  Learn more   Connection Portal  https   docs snaptrade com docs implement connection portal      Disabled Connection A connection state where brokerage authorization is invalid so fresh data and trading actions are blocked until repaired  Aliases  broken connection  disconnected connection  Learn more   Fix Disabled Connections  https   docs snaptrade com docs fix broken connections       Reconnect A re authorization flow that repairs an existing disabled connection by sending the user through the Connection Portal again  Aliases  repair flow  re authorize connection  Learn more   Fix Disabled Connections  https   docs snaptrade com docs fix broken connections      Account A specific brokerage account under a connection that SnapTrade exposes for balances  holdings  activity  and trading  Aliases  portfolio account  trading account  brokerage account  Learn more   Getting Started  Accounts  https   docs snaptrade com docs getting started getting started accounts    Account Data  https   docs snaptrade com docs account data      Balance Cash and buying power values reported for an account  Aliases  cash balance  account cash  Learn more   Account Data  Balances  https   docs snaptrade com docs account data account data balances      Position A holding of a specific asset in an account  typically represented by quantity and market value  Aliases  holding  asset position  Learn more   Account Data  Positions  https   docs snaptrade com docs account data account data positions      Order A brokerage instruction to buy or sell an instrument  including open  filled  canceled  and rejected states  Aliases  trade order  instruction  Learn more   Account Data  Orders  https   docs snaptrade com docs account data account data orders      Transaction A brokerage reported account event that records cash or position movement  such as buys  sells  dividends  fees  deposits  or withdrawals  Aliases  activity  account activity  ledger entry  Learn more   Account Data  Activities  https   docs snaptrade com docs account data account data activities      Periodic Sync The process where SnapTrade updates account data from the connected brokerage  Aliases  data refresh  update cycle  sync  Learn more   Syncing and Data Freshness  https   docs snaptrade com docs syncing      Manual Refresh An explicit API triggered sync request for a connection outside the periodic sync schedule  Aliases  forced sync  on demand refresh  Learn more   Syncing and Data Freshness  https   docs snaptrade com docs syncing      MCP Server SnapTrade s hosted Model Context Protocol server that lets AI assistants securely read a user s connected brokerage data  Aliases  AI connector  Claude connector  ChatGPT app  Learn more   SnapTrade MCP Server  https   docs snaptrade com docs mcp server  

Terminology

  Symbology  SnapTrade returns several symbol identifiers because financial instruments are not identified the same way across brokerages  exchanges  asset classes  and market data vendors  A ticker such as  AAPL  is easy to read  but it is not always enough to uniquely identify a position  match an external identifier such as an ISIN or FIGI code  or place a trade at a specific brokerage   This guide explains the main identifier types and when to use each one      Core concepts      Instrument  An  instrument  is SnapTrade s normalized representation of a financial instrument in newer account data endpoints  It is used for positions returned by endpoints such as  api AccountInformation getAllAccountPositions    Common  instrument  fields include      id   SnapTrade s UUID for the instrument     kind   the instrument type  such as  stock    etf    mutualfund    crypto    future   or  option      symbol   SnapTrade s formatted display symbol  such as  AAPL    VAB TO   or  SPY 220819P00200000      raw symbol   the base symbol without an exchange suffix     description   a human readable name     currency   the currency of the listing or contract     exchange   the exchange SnapTrade associates with the listing or contract     figi instrument   FIGI metadata when available  including  figi code  and  figi share class    The exact fields depend on  kind   For example  an option instrument includes option specific fields such as  option type    strike price    expiration date   and  underlying        Universal symbol  A  universal symbol  is SnapTrade s normalized security model used by legacy and current endpoints  It is still present in many responses and request schemas  including endpoints that refer to  universal symbol id    Common  universal symbol  fields include      id   SnapTrade s UUID for the symbol     symbol   SnapTrade s canonical display symbol  such as  AAPL    VAB TO   or  SPY      raw symbol   the base symbol without an exchange suffix  when applicable     description   a human readable security name     currency   the currency SnapTrade associates with the listing     exchange   the exchange SnapTrade associates with the listing     type   the security type     figi code   the listing level FIGI identifier when available     figi instrument   FIGI metadata when available   Do not assume that  instrument  has fully replaced  universal symbol  everywhere  Use the model returned or required by the endpoint you are calling       Canonical symbol  The  symbol  field is SnapTrade s canonical  human readable symbol or ticker for an instrument  universal symbol or option symbol  It is useful for display  search  and matching user input  Use it for display and user facing workflows  Do not use it as your only permanent cross system identifier        Stocks  ETFs and mutual funds  For stocks  ETFs  and mutual funds  SnapTrade largely follows the  Yahoo Finance ticker format  https   help yahoo com kb SLN2310 html   For example  Toronto Stock Exchange securities usually have a   TO  suffix  while NASDAQ and NYSE securities usually do not have a suffix        Options  For options   symbol  is always the  OCC option symbol  https   en wikipedia org wiki Option symbol The OCC Option Symbol   For example   SPY   220819P00200000  represents a put option on  SPY  with a strike price of  200  expiring on August 19  2022        Futures  For futures   symbol  usually includes the root symbol  month code  and year  For example   ESZ22  represents the E mini S P 500 future expiring in December 2022        Crypto  For cryptocurrencies   symbol  is not normalized between brokerages  While most brokerages supported on SnapTrade will return widely accepted symbols for the various cryptocurrencies  such as  BTC  for Bitcoin  Kraken and other exchanges may instead return  XBT  or  XXBT   These are not normalized in order to make it easier to execute crypto trading  For more details  see  api Trading searchCryptocurrencyPairInstruments  and  api Trading placeCryptoOrder        Option symbol  An  option symbol  is SnapTrade s normalized representation of a specific option contract in legacy current option related responses  While the new  api AccountInformation getAllAccountPositions  endpoint returns a discriminated union as described in the  Instrument  section  all other endpoints currently return an option symbol  We re gradually replacing this legacy construct with the newer discriminated union model   Common  option symbol  fields include      id   SnapTrade s UUID for the option contract     ticker   the OCC option symbol  such as  SPY 220819P00200000      option type    CALL  or  PUT      strike price   the strike price     expiration date   the expiration date     underlying symbol   the underlying  universal symbol    When placing option trades with  api Trading placeMlegOrder   use the OCC option symbol in  legs   instrument symbol        Brokerage instrument  A brokerage instrument describes what a brokerage can support for trading   api ReferenceData listAllBrokerageInstruments  returns brokerage level instruments with fields such as      symbol   the brokerage trading symbol  in canonical SnapTrade format     exchange mic   the exchange MIC code  when available     tradeable   whether the brokerage reports the instrument as tradeable   null  means SnapTrade does not know     fractionable   whether the brokerage reports support for fractional units   null  means SnapTrade does not know     universal symbol id   the related SnapTrade universal symbol ID  when available   Brokerage level support is not the same as account level permission  A symbol can be listed as tradable by the brokerage while a specific account is read only  restricted  or not approved for that asset class      Read use cases  When reading account data  treat SnapTrade symbol fields as normalized metadata about what the brokerage returned  Choose the identifier based on the job you are doing     Use case   Recommended fields                   Display a position or activity to a user    instrument symbol    instrument description    instrument currency   and  instrument exchange      Match a security to your own security master   Prefer  figi instrument figi code  or  figi code  when present  Otherwise use  symbol  plus  exchange   with  currency  as supporting context      Aggregate the same share class across venues   Use  figi instrument figi share class  when present  Do not treat it as a listing level identifier      Reconcile SnapTrade responses over time   Store SnapTrade s  instrument id  or  universal symbol id  when present  plus  symbol    exchange    currency   and FIGI fields        Instrument search  For stock  ETF and mutual fund trading flows  avoid depending on real time symbol search at order entry time  Instead  cache the brokerage instrument list returned by  api ReferenceData listAllBrokerageInstruments  and use that cache to resolve user input to brokerage supported symbols      Trade use cases  Trading is account specific  For order placement  use the identifier required by the trading endpoint and the connected brokerage account  Avoid using an  instrument id  or  universal symbol id  and prefer passing a symbol directly  Do not assume that every brokerage instrument is available for trade for a given account   For detailed information and recommendations around trading  see  Trading with SnapTrade  https   docs snaptrade com docs trading with snaptrade       Practical recommendations    Use  instrument  for newer account data responses and  universal symbol  where the endpoint still returns or requires it    Use  symbol  for display  user input  and standard equity order placement    Use an OCC option symbol for option quotes and option order legs    Store SnapTrade IDs when available  but keep  symbol    exchange    currency   and FIGI fields for reconciliation and debugging    Prefer FIGI for matching against external systems  Use  figi code  for listing level matching and  figi share class  for share class aggregation    Treat  tradeable  and  fractionable  as brokerage level  nullable fields   null  means unknown  

Symbology

  Sending Requests  When sending requests to SnapTrade  we recommend using an SDK  You can also send requests directly through the API reference on this site  this is especially useful for managing users and connections during development      SDKs  It is possible to integrate without an SDK  but you will need to generate a request signature for each API request  See  Request Signatures  https   docs snaptrade com docs request signatures  for the signing algorithm and code examples   SnapTrade provides the following SDKs for you to use       Language       SDK Link                     Python      https   pypi org project snaptrade python sdk    https   pypi org project snaptrade python sdk      TypeScript      https   www npmjs com package snaptrade typescript sdk    https   www npmjs com package snaptrade typescript sdk      Java      https   central sonatype com artifact com snaptrade snaptrade java sdk    https   central sonatype com artifact com snaptrade snaptrade java sdk      Ruby      https   rubygems org gems snaptrade    https   rubygems org gems snaptrade      C       https   nuget org packages SnapTrade Net    https   nuget org packages SnapTrade Net      PHP      https   packagist org packages konfig snaptrade php sdk    https   packagist org packages konfig snaptrade php sdk      Go      https   pkg go dev github com passiv snaptrade sdks sdks go    https   pkg go dev github com passiv snaptrade sdks sdks go        Ratelimiting  The SnapTrade API uses a number of safety mechanisms to protect against bursts of incoming traffic and help maximize its stability   Sending many requests in quick succession might trigger error responses that show up as HTTP status code 429      Response Headers      x request id  Each SnapTrade API request has an associated request identifier  If you need to contact us about a specific request  providing the request identifier is helpful to ensure the fastest possible resolution       x ratelimit limit  With each request  you will receive your ratelimit as a header  This denotes how many requests you can make in one minute before being throttled       x ratelimit remaining  Within each request  you will receive how many requests are remaining until SnapTrade begins throttling your requests         See also     Request Signatures  https   docs snaptrade com docs request signatures     Ratelimiting  https   docs snaptrade com docs ratelimiting     Request IDs  https   docs snaptrade com docs request ids  

Sending Requests

  Request Signatures  SnapTrade API requests are authenticated using your  clientId   a Unix  timestamp   and a  Signature  header   The official SnapTrade SDKs generate request signatures automatically  You only need to implement this flow manually if you are calling the SnapTrade API directly without an SDK      Overview  To generate a request signature   1  Build a signature payload containing the request body  path  and query string  2  Serialize the payload into canonical JSON  3  Sign the canonical JSON string using HMAC SHA256 with your  consumerKey   4  Base64 encode the HMAC digest  5  Send the encoded value in the  Signature  header      Signature Payload  The signature payload is a JSON object with exactly three fields     Field   Description                content    The JSON request body  Use  null  when the request has no body or the body is empty       path    The request path  including   api v1   excluding the query string       query    The raw query string exactly as sent in the request URL  excluding the leading         Example request      http POST  api v1 snapTrade registerUser clientId PASSIVTEST timestamp 1635790389 Signature   generated signature  Content Type  application json    userId   new user 123        The signature payload for this request is      json      content          userId    new user 123          path     api v1 snapTrade registerUser      query    clientId PASSIVTEST timestamp 1635790389            Canonical JSON Rules  Before signing  the signature payload must be serialized into a canonical JSON string   Use these rules   1  Sort object keys alphabetically at every level  2  Remove unnecessary whitespace  3  Encode the resulting string as UTF 8  4  Use  null  for empty request bodies   The canonical signature string for the example above is      json   content    userId   new user 123    path    api v1 snapTrade registerUser   query   clientId PASSIVTEST timestamp 1635790389        The following string represents the same JSON object  but it is not valid for signing because it contains extra whitespace      json   content     userId    new user 123     path     api v1 snapTrade registerUser    query    clientId PASSIVTEST timestamp 1635790389        Cryptographic signatures are generated from the exact bytes of the string  Even small formatting differences will produce a different signature      Request Details  The  query  value is the exact query string sent in the request URL  excluding the leading       Example      text  api v1 snapTrade registerUser clientId PASSIVTEST timestamp 1635790389      Use      text clientId PASSIVTEST timestamp 1635790389      Do not sort  decode  re encode  or otherwise modify query parameters before signing   For requests without body  set  content  to  null   This includes GET requests  bodyless DELETE POST requests  and requests where the body would otherwise be            Python Example     python from base64 import b64encode import hashlib import hmac import json import typing   def compute request signature path  str  consumer key  str  body  typing Any     str      subpath  query   path split          sig object              content   None if body is None or body       else body           path     api v1 s    subpath           query   query            sig content   json dumps sig object  separators             sort keys True      sig digest   hmac new consumer key encode    sig content encode    hashlib sha256  digest       return b64encode sig digest  decode     resource path     snapTrade registerUser clientId PASSIVTEST timestamp 1635790389  request body     userId    new user 123    signature   compute request signature resource path   YOUR CONSUMER KEY   request body           TypeScript Example  Node js      typescript import   as crypto from  crypto    function JSONstringifyOrder obj  Record string  unknown    string     const allKeys  string           const seen  Record string  null          JSON stringify obj  function  key  value        if    key in seen           allKeys push key         seen key    null            return value          allKeys sort      return JSON stringify obj  allKeys      function computeHmacSha256 message  string  key  string   string     const hmac   crypto createHmac  sha256   key     hmac update message     return hmac digest  base64       const consumerKey   encodeURI  YOUR CONSUMER KEY     const requestData     userId   new user 123     const requestPath     api v1 snapTrade registerUser   const requestQuery    clientId PASSIVTEST timestamp 1635790389    const sigObject       content  requestData    path  requestPath    query  requestQuery      const sigContent   JSONstringifyOrder sigObject   const signature   computeHmacSha256 sigContent  consumerKey            Java Example     java import com google gson Gson  import javax crypto Mac  import javax crypto spec SecretKeySpec  import java nio charset StandardCharsets  import java security InvalidKeyException  import java security NoSuchAlgorithmException  import java util Base64  import java util TreeMap   public class Example       private static byte   calculateHmacSha256 String message  String key              throws NoSuchAlgorithmException  InvalidKeyException           SecretKeySpec secretKeySpec   new SecretKeySpec key getBytes StandardCharsets UTF 8    HmacSHA256            Mac mac   Mac getInstance  HmacSHA256            mac init secretKeySpec           return mac doFinal message getBytes StandardCharsets UTF 8               private static String encodeBase64 byte   bytes            return Base64 getEncoder   encodeToString bytes              public static void main String   args  throws NoSuchAlgorithmException  InvalidKeyException           Gson gson   new Gson            String payload       userId     new user 123              String path     snapTrade registerUser           String queryString    clientId PASSIVTEST timestamp 1635790389           Object map   gson fromJson payload  TreeMap class           String sortedJson   map    null            gson toJson map           String data   String format     content    s   path      api v1 s     query      s                      payload    null    payload equals        payload equals          null    sortedJson  path                  queryString           String signature   encodeBase64 calculateHmacSha256 data   YOUR CONSUMER KEY                      Go Example     go package main  import     bytes    crypto hmac    crypto sha256    encoding base64    encoding json    sort    strings     func computeHmacSha256 message string  key string  string    h    hmac New sha256 New    byte key    h Write   byte message    return base64 StdEncoding EncodeToString h Sum nil      func main      requestData    map string interface    userId    new user 123    requestPath      api v1 snapTrade registerUser   requestQuery     clientId PASSIVTEST timestamp 1635790389    sigObject    map string interface       content   requestData     path      requestPath     query     requestQuery       sortedSigObject    make map string interface     keys    make   string  0  len sigObject    for k    range sigObject     keys   append keys  k      sort Strings keys   for    k    range keys     sortedSigObject k    sigObject k       var sigContent bytes Buffer  encoder    json NewEncoder  sigContent   encoder SetEscapeHTML false   encoder Encode sortedSigObject    signature    computeHmacSha256 strings TrimSuffix sigContent String      n     YOUR CONSUMER KEY        signature       

Request Signatures

  Brokerage Integrations  SnapTrade connects your app to 400M  retail investor accounts across 35  financial institutions around the world  Sometimes a single institution can have multiple integrations depending on geography or account type  For example we support Webull USA and Webull Canada as two distinct integrations  Similarly  Alpaca and Alpaca Paper are two distinct integrations despite belonging to the same company  For in depth information on each brokerage that we support  please refer to  SnapTrade Brokerage Integrations  https   support snaptrade com brokerages   

Brokerage Integrations

  Connections  A connection is an open channel for you to access the account data of your end users  Each connection is associated one to one with a set of credentials to an institution  If the access token for the connection is no longer valid  the connection will become disabled and the end user will need to go through the connection portal again to enable the connection      Connection Portal  The Connection Portal is a UI widget designed to allow end users to securely connect their brokerage accounts to your app  It handles brokerage selection  OAuth redirects  username password authentication  and multi factor auth verification in one flow      Disabled Connections  Connections can break for a variety of reasons  which are usually related to security needs  Access tokens usually have some sort of expiry associated with them  so that users occasionally need to reauthorize access in order to show that they still approve of the connection  Access tokens typically expire after a few weeks and need to be reauthorized occasionally   When an access token is no longer valid  SnapTrade considered this to be a  disabled connection  which will no longer provide live data until it is repaired by the user        See also     Fix Broken Connections  https   docs snaptrade com docs fix broken connections     Integrate the Connection Portal into Your Application  https   docs snaptrade com docs implement connection portal implement connection portal integrate the connection portal into your application  

Connections

  Account Data  An account represents a unique account at a brokerage  like an individual account  or a 401k retirement account  A connection can have multiple accounts  The same brokerage account can also belong to multiple connections  For example a joint account between two individual account holders are visible under each account holder s connection  With a connected account  you can call any SnapTrade account data API to get information about the account  its holdings  and its history      Account Details   api AccountInformation getUserAccountDetails   The account object contains information such as the institution name  the sync status of the account and the total market value of the account      Positions   api AccountInformation getUserAccountPositions   api Options listOptionHoldings   Positions are the current holdings of the account excluding cash  This includes many asset classes such as stocks  ETFs  and fixed income      Balances   api AccountInformation getUserAccountBalance   Balances are the current cash holdings and buying power of the account  In some cases  brokerages will allow holding many currencies in an account and these will be returned as separate balances      Orders   api AccountInformation getUserAccountOrders   api AccountInformation getUserAccountRecentOrders   Orders are how a broker keeps track of trading activity in an account  This differs from account activities in the following ways     Is updated intraday   Contains all orders placed at the broker regardless if they resulted in a change in position  including cancelled orders and pending orders   Often has more granular timestamps than account activities   Only looks back a few months at most     Activities   api AccountInformation getAccountActivities   Activities record the transaction history for the account  Each activity documents a change in position for the account  including deposits  withdrawals  fees  dividends  buys and sells  This differs from Orders in the following ways     Activities are updated once daily   Activities may not have timestamps of when the transaction occurred  only the date    Activities only contain transactions that resulted in a change of position to the account  no pending or cancelled orders   Often has years of history for the account  sometimes the entire account history since inception  SnapTrade classifies common transactions under the predefined types  with extra focus on what we consider the most important types  buys  sells  contributions  dividends  withdrawals  etc   When we encounter a transaction with a type that doesn t fit into one of our common types  we will return the type that the brokerage uses to identify it   We usually recommend you try not to individually handle every type beyond the most common ones  and instead rely on the other fields  amount  units  price  symbol  option symbol  etc  If amount is positive it represents gaining cash  if amount is negative it represents spending cash  Same with units  so a BUY for instance would have positive units and negative amount  a sell would be negative units positive amount   Check  our API Spec  https   docs snaptrade com reference Account 20Information AccountInformation getAccountActivities  for some of the most common transaction types        See also     Webhooks  https   docs snaptrade com docs webhooks     Getting Started with SnapTrade  https   docs snaptrade com docs getting started  

Account Data

  Syncing and Data Freshness  It s first important to understand whether you are on Pay as you Go   Real time or Pay as you Go   Daily  which you can find in  the dashboard  https   dashboard snaptrade com settings billing   Note that  if the connection is disabled  https   docs snaptrade com docs fix broken connections   fresh data cannot be fetched on either plan until the connection is fixed  Daily data is cached and refreshed once a day  Exact refresh timing may vary by brokerage   Pay as you Go   Real time  holdings  positions  balances  orders  are fetched with every API request   Pay as you Go   Daily  holdings are updated once per day with the daily sync   For both plans  transactions are cached  updated once per day with the daily sync  and delayed by one day  no intraday transactions   compare orders to transactions here  https   docs snaptrade com docs account data account data orders  if you need real time trades    If you need to know when transactions  and holdings data on Daily data plans  are synced  there are two methods   Webhooks     ACCOUNT TRANSACTIONS UPDATED  https   docs snaptrade com docs webhooks webhooks account transactions updated  webhook will be sent when we create a new transaction for an account  Note that no webhook will be sent if we sync transactions and no new data is found     ACCOUNT HOLDINGS UPDATED  https   docs snaptrade com docs webhooks webhooks account holdings updated  will be sent once per day when holdings are updated  regardless of if data changes or not   This is only really helpful for Daily data since Pay as you Go   Real time plans will update brokerage data with each request   API Account Status     List accounts for a connection endpoint  https   docs snaptrade com reference Connections Connections listBrokerageAuthorizationAccounts  will return a  sync status  object for each account in the connection  This tells you when the daily sync last ran for holdings  as well as the last day that transactions   have been fully synced    transactions have been pulled from 00 00 to 23 59   If a user has multiple connections  first call  api Connections listBrokerageAuthorizations   then call  api Connections listBrokerageAuthorizationAccounts  for each connection           sync status            transactions              initial sync completed   true           last successful sync    2022 01 24            first transaction date    2022 01 24                  holdings              initial sync completed   true           last successful sync    2024 06 28 18 42 46 561408 00 00                        If on Pay as you Go   Daily and a holdings update is needed  you can call  the Refresh connection endpoint  https   docs snaptrade com reference Connections Connections refreshBrokerageAuthorization   Please note that additional charges may apply to each of these calls  you can find pricing information in  the dashboard  https   dashboard snaptrade com settings billing    If looking to control at what time of day transactions are updated  please reach out to the team about  a custom plan  https   snaptrade com pricing   

Syncing and Data Freshness

  Request IDs  Each SnapTrade API request has an associated request identifier   You can find this value in the response headers  under  X Request ID   For example  running a simple  curl  request and glancing at the headers for the response will give something like this       curl  v https   api snaptrade com api v1         date  Fri  13 Oct 2023 00 32 06 GMT   content type  application json   content length  71   server  gunicorn   vary  Accept  DNT  origin  Cookie   allow  GET  HEAD  OPTIONS   x frame options  DENY   x request id  27fcf193c58c4a646aa9fd90e833ab29   x content type options  nosniff   referrer policy  same origin   cross origin opener policy  same origin      If you need to contact us about a specific request  providing the request identifier will ensure the fastest possible resolution  

Request IDs

  Fix Disabled Connections  A SnapTrade connection provides direct access to a user s trading account  When an access token is no longer valid  SnapTrade considered this to be a  disabled connection  which will no longer provide live data until it is repaired by the user     Required Functionalities  It is important that users are directed to  fix connections  rather than they create new ones  This allows you to provide a better experience to the user  minimize the number of disabled connections you are managing  and retain historical session data  Using the Connection Portal in the normal manner will create new connections  which will have a different connection id and different account ids if successful  as well as will leave the disabled connection to remain   It is a requirement to implement the ability to reconnect so that connections can be fixed  There are mechanisms available to be notified when connections break  either through a   webhooks   docs webhooks  as described below  or b  by polling the connections endpoint   api Connections listBrokerageAuthorizations   for each user and checking the  disabled  status  When  disabled    true   the connection is disabled and the user must take an action to fix it     How to fix a disabled connection  SnapTrade s Connection Portal has a special mode that s designed for fixing connections  rather than creating new ones  To use the reconnect mode  you simply pass along the connection id in the  reconnect  field as part of the request to generate a login link  See  api Authentication loginSnapTradeUser    When the Connection Portal is accessed with the  reconnect  parameter  it will immediately take the user into the appropriate reconnection flow for that connection  When successful  the disabled connection will be updated with a new access token and start working again   Note  It is important that the user logs into the same brokerage connection when attempting to reconnect  Changing the connection in a reconnect is not permitted and will return an error  If the user wishes to change the connection  they should delete the old connection and create a new one to the new trading account     Webhooks  SnapTrade provides webhooks to notify when new connections are     Attempted   Added   Updated   Deleted   Broken   Fixed  If you have a webhook listener URL associated with your SnapTrade account  you will automatically receive webhook events to let you know when any of those events take place  This is especially useful for noticing when connections break so that you can inform the user that they need to reconnect   Review the documentation on  SnapTrade Webhooks   docs webhooks  for more detail  sample payloads  etc  

Fix Disabled Connections

  Frequently Asked Questions  Need a quick definition while reading  See  Terminology  https   docs snaptrade com docs terminology       API Keys      I have lost the consumerKey to my API Key  What should I do   You should reach out to SnapTrade support  If it is compromised  your users are still safe due to also requiring a user secret to get account data or place trades           Requests      I am getting a  Unable to verify signature sent  error when making a request to the API  What should I do   The API call is failing when comparing the expected signature to the signature provided by your client  This can happen for many reasons  but is likely caused by attempting to configure the signature without an SDK  or an invalid consumerKey  If you need to reset your consumerKey  reach out to someone in SnapTrade staff           Users      What is a  Connected User    A connected user is a user who has at least one connection  If someone connects both a Wealthsimple Trade and Questrade account  then that person will be counted as one connected user  Similarly if they have multiple accounts  IRA and margin  at one broker  then that s also counted as one connected user   A user is considered a connected user from the moment they successfully complete the first connection process to when you or the user deletes their last connection  some times users have multiple brokers connected   You can handle this on your end or let the users delete the connections from your platform       What should I do if I lose the userSecret of one of my users   If you lose the userSecret the easiest thing to do is create a new user and ask the end user to reconnect         The userSecret to one of my SnapTrade users has been compromised  What should I do     The best thing to do in this case is to rotate the user secret using  api Authentication resetSnapTradeUserSecret            Connections      What is the format of   disabled date     All of our timestamp fields return datetime in ISO 8601 format       What is the difference between an account and a connection     image png    assets 250312 model png   The accounts live under the connection to the brokerage  Each connection is associated one to one with a set of credentials to the brokerage  When you create a connection  SnapTrade will automatically sync all accounts under the set of credentials to the brokerage  For example  if you made a new connection to Questrade  a Canadian brokerage  and that connection had a TFSA  an RRSP and an FHSA account under those credentials  SnapTrade would make all these accounts accessible over the SnapTrade API       If I want to remove an account do I need to delete the connection   If you want to remove an account  you will need to delete the corresponding connection  You can do this using  api Connections removeBrokerageAuthorization        If I delete connection  will it delete all accounts from that Connection  Can I delete only one account   Deleting the connection will remove all accounts under that connection  Instead of deleting individual accounts  you could mark them as hidden on your end and only pull information from accounts that are not hidden       How can I force a connection to become disabled for testing   You can do this with the  api Connections disableBrokerageAuthorization  endpoint       How do I enable connecting to  X  broker on my API Key   By default  all brokers which can be enabled for you are enabled  For now  broker configuration is done manually on our end  Certain brokers require an application to enable the integration  Alpaca  Tradier  Tradestation  Questrade  Fidelity   Please reach out if you need access to one of these           Account Information      What kind of accounts does SnapTrade support   We support all kinds of accounts and it is brokerage dependent  In general  if the brokerage returns it to us  we will return it over the API  You can refer to the  SnapTrade Broker Support Matrix  https   support snaptrade com brokerages  and the field will be returned over the  raw type  on the account object       How do I determine if an activity indicates the position was bought or sold   If the activity resulted in a gain in position to the account  long   the activity will have a positive unit  If the activity resulted in a loss of position to the account  short   the activity will have a negative unit       Is it possible to know a stock s first purchase date   Determining a stock s first purchase date varies by brokerage  Two key requirements must be met   1  The brokerage must provide activities or transaction data that includes historical buy sell records  2  The brokerage must include complete transaction history in the account data   Some brokerages have data retention limits for example  Schwab only provides up to 4 years of historical data  You can check this here  SnapTrade Broker Support Matrix  https   support snaptrade com brokerages       When does account data get synced daily   It is not consistent at the same time every day  but guarunteed once per day       My account data is stale  why is my account not syncing every day   The connection is probably disabled  this happens when the access token is no longer valid  Please check using the  api Connections detailBrokerageAuthorization  and follow  this guide  https   docs snaptrade com docs fix broken connections  to repair the connection       How can I tell the difference between asset classes   Each symbol will have a  type  property  This will contain a short code representing the security type  For example   cs  for Common Stock  Here are some common values    ad    ADR  bnd    Bond  cs    Common Stock  cef    Closed End Fund  crypto    Cryptocurrency  et    ETF  oef    Open Ended Fund  ps    Preferred Stock  rt    Right  struct    Structured Product  ut    Unit  wi    When Issued  wt    Warrant          Trading      Is there a comprehensive list of symbol IDs that I can use for submitting trades   A symbol is not guaranteed to be stable  Since a stock is able to be traded on multiple exchanges  you should get the symbol with  api Trading getUserAccountQuotes  at the time you want to place the trade       

Frequently Asked Questions

  Sandbox  A simulated brokerage for exercising your integration end to end   connection flow  accounts  balances  holdings  orders  and transactions   without a real brokerage login  It returns deterministic data and lets you trigger specific success and failure outcomes      Getting access    Sandbox is available on   non production   keys   both   personal keys   and   commercial test keys     and is   enabled by default    so there s nothing to request    It is   not available on commercial production keys    and can t be enabled on them    In the connection portal it s flagged   For testing only     pinned to the   top   of the institution list on commercial test keys  and shown at the   bottom   on personal keys     Sandbox in the connection portal  flagged  For testing only     assets sandbox portal png      Connecting  1  Generate a Connection Portal URL as usual   loginSnapTradeUser   and use a   read   connection type  Optionally pass  broker SANDBOX  to jump straight past the institution list  skipping step 2  2  Select   Sandbox    3  Pick a   scenario   to simulate     Connect        Scenarios    Data   connection succeeds         Self directed    default    2 funded accounts with positions  orders  and transaction history     Cash only     1 cash account  no holdings     No transactions     accounts with positions but no activity history     No accounts     succeeds but returns zero accounts    Errors   connection fails         Invalid credentials     invalid credentials error     Account locked     account locked error     Rate limited     rate limit error     What the data covers  data scenarios     Accounts  balances  cash   buying power   and positions across a handful of well known tickers   Orders spanning every status   executed  partially filled  accepted  canceled  rejected   Transactions spanning   trades      cash   fees      dividends   income      corporate actions    and   transfers    see the full list of types below    In the default   Self directed   scenario these are   spread across the two accounts    e g  splits   dividends on one  transfers   mergers on the other    iterate   all   accounts to see the full set   details   summary  b All transaction types  b   summary   These are the normalized  type  values SnapTrade maps real brokerage transactions to  the Sandbox exercises most of them across its data scenarios   The list is   not exhaustive    when a brokerage transaction doesn t map to one of these  SnapTrade returns the raw type the brokerage uses  so treat  type  as open ended and lean on  amount    units    price   and  symbol  where you can     Category   Type   Description                         Trades    BUY    Asset bought      Trades    SELL    Asset sold      Cash   fees    CONTRIBUTION    Cash contribution  deposit  into the account      Cash   fees    WITHDRAWAL    Cash withdrawal from the account      Cash   fees    INTEREST    Interest deposited into the account      Cash   fees    FEE    Fee withdrawn from the account      Cash   fees    TAX    A tax related fee      Cash   fees    REBATE    A rebate credited to the account      Dividends   income    DIVIDEND    Dividend payout      Dividends   income    REI    Dividend reinvestment      Dividends   income    STOCK DIVIDEND    Dividend distributed as shares instead of cash      Dividends   income    RETURN OF CAPITAL    Return of capital distribution      Dividends   income    DISTRIBUTION    A distribution paid into the account      Options    OPTIONEXPIRATION    Option expiration event      Options    OPTIONASSIGNMENT    Option assignment event      Options    OPTIONEXERCISE    Option exercise event      Corporate actions    SPLIT    A stock share split      Corporate actions    REVERSE SPLIT    A reverse stock share split      Corporate actions    SPINOFF    Shares received from a corporate spinoff      Corporate actions    STOCK MERGER    Shares resulting from a merger      Corporate actions    ADJUSTMENT    A one time adjustment of the account s cash balance or shares of an asset      Transfers    TRANSFER    Transfer of asset s  from one account to another      Transfers    EXTERNAL ASSET TRANSFER IN    Incoming transfer of an asset from an external account      Transfers    EXTERNAL ASSET TRANSFER OUT    Outgoing transfer of an asset to an external account      Transfers    INTERNAL CASH TRANSFER IN    Incoming cash transfer between your own accounts      Transfers    INTERNAL CASH TRANSFER OUT    Outgoing cash transfer between your own accounts      Transfers    INTERNAL ASSET TRANSFER IN    Incoming asset transfer between your own accounts      Transfers    INTERNAL ASSET TRANSFER OUT    Outgoing asset transfer between your own accounts       details      Limitations      Read only     placing canceling trades isn t supported  and Sandbox won t appear in   trade only   connection sessions   Data is   static and simulated    timestamps are relative to the current time  

Sandbox

Check whether the API is operational and verify timestamps.

Get API Status

Returns a list of all registered user IDs. Please note that the response is not currently paginated.

List all users

Registers a new SnapTrade user under your Client ID. A user secret will be automatically generated for you and must be properly stored in your system.
Most SnapTrade operations require a user ID and user secret to be passed in as parameters.


Register user

Deletes a registered user and all associated data. This action is irreversible. This API is asynchronous and will return a 200 status code if the request is accepted. The user and all associated data will be queued for deletion. Once deleted, a `USER_DELETED` webhook will be sent.

Delete user

Authenticates a SnapTrade user and returns the Connection Portal URL used for connecting brokerage accounts. Please check [this guide](/docs/implement-connection-portal) for how to integrate the Connection Portal into your app.

Please note that the returned URL expires in 5 minutes.


Generate Connection Portal URL

Rotates the secret for a SnapTrade user. You might use this if `userSecret` is compromised. Please note that if you call this endpoint and fail to save the new secret, you'll no longer be able to access any data for this user, and your only option will be to delete and recreate the user, then ask them to reconnect.


Rotate user secret

Returns configurations for your SnapTrade Client ID, including allowed brokerages and data access.

Get Client Info

Returns active Trade Detection subscriptions for your Client ID. Cancelled subscriptions are not returned.

List active Trade Detection subscriptions

Adds or restores a Trade Detection subscription for a connected brokerage account.
This endpoint requires `userId` and `userSecret` in addition to the partner signature.


Add a Trade Detection subscription

Cancels a Trade Detection subscription for a connected brokerage account.
This endpoint requires partner signature authentication only and does not require `userId` or `userSecret`.


Cancel a Trade Detection subscription

**Deprecated, please use the account-specific holdings endpoint instead.**

List all accounts for the user, plus balances, positions, and orders for each
account.

**Note:** This endpoint will return HTTP 410 Gone for all customers that sign up after April 25, 2026.


List all accounts for the user, plus balances, positions, and orders for each account.

**Deprecated.** Use the finer-grained account data endpoints instead: [balances](/reference/Account%20Information/AccountInformation_getUserAccountBalance), [positions](/reference/Account%20Information/AccountInformation_getAllAccountPositions), and [orders](/reference/Account%20Information/AccountInformation_getUserAccountOrders).
Returns a list of balances, positions, and recent orders for the specified account.

Check your API key on the [Customer Dashboard billing page](https://dashboard.snaptrade.com/settings/billing) to see if you have real-time data access:
  - If you do, this endpoint returns real-time data.
  - If you don't, Daily data is cached and refreshed once a day. Exact refresh timing may vary by brokerage. If you need real-time, use the [manual refresh](/reference/Connections/Connections_refreshBrokerageAuthorization) endpoint.

If the connection has become disabled, it can no longer access the latest data from the brokerage, but will continue to return the last available cached state. Please see [this guide](/docs/fix-broken-connections) on how to fix a disabled connection.


List account holdings

Returns all brokerage accounts across all connections known to SnapTrade for the authenticated user.

This endpoint returns Daily data regardless of the customer's plan. Daily data is cached and refreshed once a day, which makes this endpoint fast and well-suited to listing accounts across all of a user's connections in a single call. Exact refresh timing may vary by brokerage. To get real-time data on Pay as you Go / Real-time, use the [list accounts for a connection endpoint](/reference/Connections/Connections_listBrokerageAuthorizationAccounts). Customers on Pay as you Go / Daily can force a refresh with the [manual refresh endpoint](/reference/Connections/Connections_refreshBrokerageAuthorization).


List accounts

Returns account detail known to SnapTrade for the specified account.

Check your API key on the [Customer Dashboard billing page](https://dashboard.snaptrade.com/settings/billing) to see if you have real-time data access:
  - If you do, this endpoint returns real-time data.
  - If you don't, Daily data is cached and refreshed once a day. Exact refresh timing may vary by brokerage. If you need real-time, use the [manual refresh](/reference/Connections/Connections_refreshBrokerageAuthorization) endpoint.

If the connection has become disabled, it can no longer access the latest data from the brokerage, but will continue to return the last available cached state. Please see [this guide](/docs/fix-broken-connections) on how to fix a disabled connection.


Get account detail

Updates various properties of a specified account.

Update details of an investment account

Returns a list of balances for the account. Each element of the list has a distinct currency. Some brokerages like Questrade [allows holding multiple currencies in the same account](https://www.questrade.com/learning/questrade-basics/balances-and-reports/understanding-your-account-balances).

Check your API key on the [Customer Dashboard billing page](https://dashboard.snaptrade.com/settings/billing) to see if you have real-time data access:
  - If you do, this endpoint returns real-time data.
  - If you don't, Daily data is cached and refreshed once a day. Exact refresh timing may vary by brokerage. If you need real-time, use the [manual refresh](/reference/Connections/Connections_refreshBrokerageAuthorization) endpoint.

If the connection has become disabled, it can no longer access the latest data from the brokerage, but will continue to return the last available cached state. Please see [this guide](/docs/fix-broken-connections) on how to fix a disabled connection.


List account balances

Returns a list of stock/ETF/crypto/mutual fund positions in the specified account. For option positions, please use the [options endpoint](/reference/Options/Options_listOptionHoldings).

This endpoint is deprecated. Consider using the newer [unified positions endpoint](/reference/Account%20Information/AccountInformation_getAllAccountPositions). This will allow you to get both equity and option positions in a single call, as well as additional asset classes such as futures.

Check your API key on the [Customer Dashboard billing page](https://dashboard.snaptrade.com/settings/billing) to see if you have real-time data access:
  - If you do, this endpoint returns real-time data.
  - If you don't, Daily data is cached and refreshed once a day. Exact refresh timing may vary by brokerage. If you need real-time, use the [manual refresh](/reference/Connections/Connections_refreshBrokerageAuthorization) endpoint.

If the connection has become disabled, it can no longer access the latest data from the brokerage, but will continue to return the last available cached state. Please see [this guide](/docs/fix-broken-connections) on how to fix a disabled connection.


List account positions

Returns a list of all positions in the specified account.

The `results` list can contain multiple instrument types in the same response, including stocks, ADRs, ETFs, mutual funds, closed-end funds, crypto, futures, option positions, and CFD positions. Use the `instrument.kind` discriminator to determine the schema for each position's `instrument`.

`mutualfund` positions may also include `cash_equivalent`. `stock` positions may include `tax_lots` when tax lot data is enabled for the account.

If the connection has become disabled, it can no longer access the latest data from the brokerage, but will continue to return the last available cached state. Please see [this guide](/docs/fix-broken-connections) on how to fix a disabled connection.


List all account positions

Returns a list of recent orders in the specified account.

Check your API key on the [Customer Dashboard billing page](https://dashboard.snaptrade.com/settings/billing) to see if you have real-time data access:
  - If you do, this endpoint returns real-time data.
  - If you don't, Daily data is cached and refreshed once a day. Exact refresh timing may vary by brokerage. If you need real-time, use the [manual refresh](/reference/Connections/Connections_refreshBrokerageAuthorization) endpoint.

If the connection has become disabled, it can no longer access the latest data from the brokerage, but will continue to return the last available cached state. Please see [this guide](/docs/fix-broken-connections) on how to fix a disabled connection.


List account orders

Returns a list of recent orders in the specified account.

The V2 order response format will include all legs of each order in the `legs` list field. If the order is single legged, `legs` will be a list of one leg.

If the connection has become disabled, it can no longer access the latest data from the brokerage, but will continue to return the last available cached state. Please see [this guide](/docs/fix-broken-connections) on how to fix a disabled connection.


List account orders v2

An experimental endpoint that returns estimated historical total account value for the specified account. Total account value is the sum of the market value of all positions and cash in the account at a given time. This endpoint is experimental, disabled by default, and has a maximum lookback of 1 year.


List historical account total value

A lightweight endpoint that returns the latest page of orders placed in the last 24 hours in the specified account. For most brokerages, the default page size is 100 meaning the endpoint will return a max of 100 orders.
This endpoint is realtime and can be used to quickly check if account state has recently changed due to an execution, or check status of recently placed orders
Differs from /orders in that it is always realtime, and only checks the last 24 hours
By default only returns executed orders, but that can be changed by setting *only_executed* to false


List account recent orders (last 24 hours only)

A lightweight endpoint that returns a list of orders executed in the last 24 hours in the specified account using the V2 order format.
This endpoint is realtime and can be used to quickly check if account state has recently changed due to an execution, or check status of recently placed orders.
Differs from /orders in that it is realtime, and only checks the last 24 hours as opposed to the last 30 days.
By default only returns executed orders, but that can be changed by setting *only_executed* to false.
**Because of the cost of realtime requests, each call to this endpoint incurs an additional charge. You can find the exact cost for your API key on the [Customer Dashboard billing page](https://dashboard.snaptrade.com/settings/billing)**


List account recent orders (V2, last 24 hours only)

Returns a list of rate of return percents for a given account.


List account rate of returns

Returns all historical transactions for the specified account.

This endpoint is paginated with a default page size of 1000. The endpoint will return a maximum of 1000 transactions per request. See the query parameters for pagination options.

Transaction are returned in reverse chronological order, using the `trade_date` field.

This endpoint returns Daily data. Daily data is cached and refreshed once a day. Exact refresh timing may vary by brokerage.

If the connection has become disabled, it can no longer access the latest data from the brokerage, but will continue to return the last available cached state. Please see [this guide](/docs/fix-broken-connections) on how to fix a disabled connection.


List account activities

Returns a list of rate of return percents for a given connection.


List connection rate of returns

Returns a maximum of 10 quotes from the brokerage for the specified symbols and account.

The quotes returned can be delayed depending on the brokerage the account belongs to. It is highly recommended that you use your own market data provider for real-time quotes instead of relying on this endpoint.

**This endpoint is not a substitute for a market data provider. Frequent polling of this endpoint may result in the disabling of your keys**

This endpoint does not work for options quotes.

This endpoint is disabled for free plans by default. Please contact support to enable this endpoint if needed.


Get equity symbol quotes

Returns a quote for a single option contract. The option contract is specified using in the 21 character OCC format. For example `AAPL  251114C00240000` represents a call option on AAPL expiring on 2025-11-14 with a strike price of $240. For more information on the OCC format, see [here](https://en.wikipedia.org/wiki/Option_symbol#OCC_format)
**Note:** These are derived values and are not suitable for trading purposes.


Get option quote

**This endpoint is deprecated. Please switch to [the new cancel order endpoint](/reference/Trading/Trading_cancelOrder) **
Attempts to cancel an open order with the brokerage. If the order is no longer cancellable, the request will be rejected.


Cancel equity order

Returns a list of Universal Symbol objects that match the given query. The matching takes into consideration both the ticker and the name of the symbol. Only the first 20 results are returned.

The search results are further limited to the symbols supported by the brokerage for which the account is under.


Search account symbols

Returns a list of option positions in the specified account. For stock/ETF/crypto/mutual fund positions, please use the [positions endpoint](/reference/Account%20Information/AccountInformation_getUserAccountPositions).

This endpoint is deprecatd. Consider using the newer [unified positions endpoint](/reference/Account%20Information/AccountInformation_getAllAccountPositions). This will allow you to get both equity and option positions in a single call, as well as additional asset classes such as futures.

Check your API key on the [Customer Dashboard billing page](https://dashboard.snaptrade.com/settings/billing) to see if you have real-time data access:
  - If you do, this endpoint returns real-time data.
  - If you don't, Daily data is cached and refreshed once a day. Exact refresh timing may vary by brokerage. If you need real-time, use the [manual refresh](/reference/Connections/Connections_refreshBrokerageAuthorization) endpoint.


List account option positions

Returns a list of all connections for the specified user. Note that `Connection` and `Brokerage Authorization` are interchangeable, but the term `Connection` is preferred and used in the doc for consistency.

A connection is usually tied to a single login at a brokerage. A single connection can contain multiple brokerage accounts.

SnapTrade performs de-duping on connections for a given user. If the user has an existing connection with the brokerage, when connecting the brokerage with the same credentials, SnapTrade will return the existing connection instead of creating a new one.


List all connections

Deletes the SnapTrade connection specified by the ID. This will also remove the accounts and holdings data associated with the connection from SnapTrade. This action is irreversible. This endpoint is synchronous, a 204 response indicates that the data has been successfully deleted.

Delete connection

Returns a single connection for the specified ID.

Get connection detail

Deletes the SnapTrade connection specified by the ID. This will also remove the accounts and holdings data associated with the connection from SnapTrade. This action is irreversible. This endpoint is asynchronous, a 200 response indicates that a task has been queued to delete the connection. Listen for the [`CONNECTION_DELETED` webhook](https://docs.snaptrade.com/docs/webhooks#webhooks-connection_deleted) webhook to know when the deletion has been completed and the data has been removed.

Trigger a holdings update for all accounts under this connection. Updates will be queued asynchronously. [`ACCOUNT_HOLDINGS_UPDATED` webhook](/docs/webhooks#webhooks-account_holdings_updated) will be sent once the sync completes for each account under the connection.
This endpoint will also trigger a transaction sync for the past day if one has not yet occurred.

**Because of the cost of refreshing a connection, each call to this endpoint incurs an additional charge. You can find the exact cost for your API key on the [Customer Dashboard billing page](https://dashboard.snaptrade.com/settings/billing)**
**Please note this endpoint is disabled for Real-time plans (Personal and Pay as you go) unless the connection is delayed. Real-time connections do not benefit from this feature since data is refreshed when calls are made. Refer to the `data_freshness_mode` field on a connection to determine this.**


Refresh holdings for a connection

Trigger a transactions sync for all accounts under this connection. Updates will be queued asynchronously. Transactions are not updated intra-day, but calling this endpoint can ensure that the previous day's transactions have been synced. For more information on sync behaviour, see: https://docs.snaptrade.com/docs/syncing


Sync transactions for a connection

Manually force the specified connection to become disabled. This should only be used for testing a reconnect flow, and never used on production connections.
Will trigger a disconnect as if it happened naturally, and send a [`CONNECTION_BROKEN` webhook](/docs/webhooks#webhooks-connection_broken) for the connection.

This endpoint is available on test keys. If you would like it enabled on production keys as well, please contact support as it is disabled by default.


Force disable connection

Returns all brokerage accounts that belong to the specified connection for the authenticated user.

On Pay as you Go / Real-time, this endpoint refreshes each account's opening date, funding date, and total value live from the brokerage on each call.

On Pay as you Go / Daily, this endpoint returns Daily data. Daily data is cached and refreshed once a day. Exact refresh timing may vary by brokerage. To force a refresh, use the [manual refresh endpoint](/reference/Connections/Connections_refreshBrokerageAuthorization).

Check your API key on the [Customer Dashboard billing page](https://dashboard.snaptrade.com/settings/billing) to see whether your plan includes real-time data.


List accounts for a connection

Returns a list of session events associated with a user.

Get all session events for a user

Returns a list of all defined Brokerage objects.

Get brokerages

Returns a list of all brokerage instruments available for a given brokerage. Not all brokerages support this. The ones that don't will return an empty list.

Get brokerage instruments

Returns a list of all defined Brokerage authorization Type objects.

Get all brokerage authorization types

Returns a list of all defined Currency objects.

Get currencies

Returns a list of all Exchange Rate Pairs for all supported Currencies.

Get currency exchange rates

Returns an Exchange Rate Pair object for the specified Currency Pair.

Get exchange rate of a currency pair

Returns a list of all supported Exchanges.

Get exchanges

Return all available security types supported by SnapTrade.

List security types

Returns a list of Universal Symbol objects that match the given query. The matching takes into consideration both the ticker and the name of the symbol. Only the first 20 results are returned.


Search symbols

Returns the Universal Symbol object specified by the ticker or the Universal Symbol ID. When a ticker is specified, the first matching result is returned. We largely follow the [Yahoo Finance ticker format](https://help.yahoo.com/kb/SLN2310.html)(click on "Yahoo Finance Market Coverage and Data Delays"). For example, for securities traded on the Toronto Stock Exchange, the symbol has a '.TO' suffix. For securities traded on NASDAQ or NYSE, the symbol does not have a suffix. Please use the ticker with the proper suffix for the best results.


Get symbol detail

Places a brokerage order in the specified account. The order could be rejected by the brokerage if it is invalid or if the account does not have sufficient funds.

This endpoint does not compute the impact to the account balance from the order and any potential commissions before submitting the order to the brokerage. If that is desired, you can use the [check order impact endpoint](/reference/Trading/Trading_getOrderImpact).

It's recommended to trigger a manual refresh of the account after placing an order to ensure the account is up to date. You can use the [manual refresh](/reference/Connections/Connections_refreshBrokerageAuthorization) endpoint for this.


Place equity order

**This endpoint is deprecated. Please switch to [the new complex order endpoint](/reference/Trading/Trading_placeComplexOrder) **
Places a bracket order (entry order + OCO of stop loss and take profit). Disabled by default please contact support for
use. Only supported on certain brokerages


Place bracket order

Places a complex conditional order (OCO, OTO, or OTOCO).
Only supported on certain brokerages.
Please refer to the [brokerage trading support page](https://support.snaptrade.com/brokerages) for details on which brokerages support complex orders and which types they support.

- **OCO** (One Cancels the Other): Two peer orders; when one fills the other is cancelled.
- **OTO** (One Triggers the Other): A trigger order that, when filled, activates a conditional order.
- **OTOCO** (One Triggers a One Cancels the Other): A trigger order that, when filled, activates an OCO pair of two peer orders.


Place complex order

Replaces an existing pending order with a new one. The way this works is brokerage dependent, but usually involves cancelling
the existing order and placing a new one. The order's brokerage_order_id may or may not change, be sure to use the one
returned in the response going forward. Only supported on some brokerages


Replace order

Simulates an order and its impact on the account. This endpoint does not place the order with the brokerage. If successful, it returns a `Trade` object and the ID of the object can be used to place the order with the brokerage using the [place checked order endpoint](/reference/Trading/Trading_placeOrder). Please note that the `Trade` object returned expires after 5 minutes. Any order placed using an expired `Trade` will be rejected.

Check equity order impact

Places the previously checked order with the brokerage. The `tradeId` is obtained from the [check order impact endpoint](/reference/Trading/Trading_getOrderImpact). If you prefer to place the order without checking for impact first, you can use the [place order endpoint](/reference/Trading/Trading_placeForceOrder).

It's recommended to trigger a manual refresh of the account after placing an order to ensure the account is up to date. You can use the [manual refresh](/reference/Connections/Connections_refreshBrokerageAuthorization) endpoint for this.


Place checked equity order

Returns the detail of a single order using the external order ID provided in the request body.

This endpoint only works for single-leg orders at this time. Support for multi-leg orders will be added in the future.

This endpoint is always realtime and does not rely on cached data.

This endpoint only returns orders placed through SnapTrade. In other words, orders placed outside of the SnapTrade network are not returned by this endpoint.


Get account order detail

Returns the detail of a single order using the brokerage order ID provided as a path parameter.

The V2 order response format includes all legs of the order in the `legs` list field.
If the order is single legged, `legs` will be a list of one leg.

This endpoint is always realtime and does not rely on cached data.

This endpoint only returns orders placed through SnapTrade. In other words, orders placed outside of the SnapTrade network are not returned by this endpoint.


Get account order detail (V2)

Places an order in the specified account.
This endpoint does not compute the impact to the account balance from the order before submitting the order.


Place crypto order

Cancels an order in the specified account. Accepts order IDs for all asset types.


Cancel order

Previews an order using the specified account.


Preview crypto order

Searches cryptocurrency pairs instruments accessible to the specified account. Both `base` and `quote` are optional. Omit both for a full list of cryptocurrency pairs.


Get crypto pairs

Get crypto pair quote

Simulates an option order with up to 4 legs and returns the estimated cost and transaction fees without placing it.
Only supported for certain enabled brokerages. Please refer to the [brokerage trading support page](https://support.snaptrade.com/brokerages) for more information on which brokerages support this endpoint.


Get option order impact

Places a multi-leg option order. Only supported on certain option trading brokerages. https://support.snaptrade.com/brokerages has information on brokerage trading support


Place option order

This endpoint is being deprecated but will continue to be available for use via SDKs, please use [the account level endpoint](/reference/Account%20Information/AccountInformation_getAccountActivities) if possible

Returns all historical transactions for the specified user and filtering criteria. It's recommended to use `startDate` and `endDate` to paginate through the data, as the response may be very large for accounts with a long history and/or a lot of activity. There's a max number of 10000 transactions returned per request.

There is no guarantee to the ordering of the transactions returned. Please sort the transactions based on the `trade_date` field if you need them in a specific order.

This endpoint returns Daily data. Daily data is cached and refreshed once a day. Exact refresh timing may vary by brokerage.

**Note:** This endpoint will return HTTP 410 Gone for all customers that sign up after April 25, 2026.


Get transaction history for a user

Returns performance information (contributions, dividends, rate of return, etc) for a specific timeframe. Please note that Total Equity Timeframe and Rate of Returns are experimental features. Please contact support@snaptrade.com if you notice any inconsistencies.

Get performance information for a specific timeframe

A webhook that is sent whenever a new connection is added.

/connectionAdded

A webhook that is sent whenever an existing connection is deleted.

/connectionDeleted

A webhook that is sent whenever a user is newly registered.

/userRegistered

A webhook that is sent whenever an existing user is deleted.

/userDeleted

A webhook that is sent whenever a new account is added to an existing brokerage authorization.

/accountAdded

A webhook that is sent whenever an existing account under a brokerage authorization is deleted.

/accountDeleted

A webhook that is sent whenever transactions have been updated for an account.

/transactionsUpdated

PartnerSignature

PartnerTimestamp

import { Snaptrade } from "snaptrade-typescript-sdk";

const snaptrade = new Snaptrade({
  clientId: "PARTNER_CLIENT_ID",
  consumerKey: "CONSUMER_KEY",
});

const response =
  await snaptrade.authentication.listSnapTradeUsers();
console.log(response.data);


from pprint import pprint
from snaptrade_client import SnapTrade

snaptrade = SnapTrade(
    client_id="PARTNER_CLIENT_ID",
    consumer_key="CONSUMER_KEY"
)

response = snaptrade.authentication.list_snap_trade_users()
pprint(response.body)

List all users

Execute an API Request

Response fields