We built our API with the goal that our developers and partners will love working with it as much as we do. We hope we've made it intuitive and easy to use, but where a bit more explanation is required, the documentation should answer any questions you might have. Of course, we'll do our best to answer any questions you have by submitting them to


  • User and Account Data

    You can fetch balances, positions, activity, orders using a user or account number. This allows you to make the most efficient use of the API.

  • Watchlists

    Watchlists are a great way to let users keep track of their interests. You can create, update, and delete watchlists and all items within them.

  • Streaming Events

    Get live updates to orders and market data in real-time -- as the events happen. Just open the feed and listen for what you're interested in.

  • Trading

    Execute simple and complex orders in an easy to use trading interface. Simple request payloads using form parameters, eliminating the need for complex XML.

  • Real-time Market Data

    Market data delivered in real-time through HTTP request/response. This includes equity and option quotes, chains, expirations, strikes, and tick-based time and sales.

  • Historical Data

    We offer historical tick data for 5 days and long-term historical data spanning back as far as possible.


Great products are built with great customers. That means when things don't work the way you expect (or want), letting us know. We'll do our very best to incorporate features and changes as quickly as possible.

If you find something isn't meeting your expectations, send an email to

Using this documentation

All of Tradier's APIs are implemented using industry-standards formats, documentation, and best practices to make integrating as easy as possible. We hope you find that our decisions in both practice and implementation meets and exceeds your standards.

We've broken each API resource into a section. Within each section, each call is labeled and documented based on its intended use. On each documentation page where an API call is referenced, there are three sections: request, response, example.

All the information you'll need to make this request within your application
Information about the fields and errors returned by this API call
An example CURL request to this API resource including: command, request, and response.

Tradier Inc. and its corresponding technology services (including API services) are distinct and separate from the services provided by Tradier Brokerage Inc. For more information regarding the services of Tradier, Inc., please contact For more information regarding the services of Tradier Brokerage, Inc. please contact Tradier Brokerage Inc. Member FINRA/SIPC

© 2019 Tradier Inc.
  • 11016 Rushmore Drive, Suite 350
  • Charlotte, NC 28277

All materials contained on this site and specifically the API documentation pages are protected by United States copyright law and may not be copied, reproduced, distributed, transmitted, displayed, published or broadcast without the prior written permission of Tradier Inc. The Structure, Format, Layout, Examples and Design of the pages are owned by Tradier Inc, and any efforts to willfully or accidently duplicate a whole or part of the pages on this site is a violation of United States copyright law.