> For the complete documentation index, see [llms.txt](https://turboflow.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://turboflow.gitbook.io/whitepaper/turboflow/professional-access/api-trading.md). # API Trading Programmatic trading access for professional and high-volume TurboFlow traders. ### Overview The TurboFlow Trading API provides programmatic access for professional and high-volume traders looking to integrate TurboFlow into their trading systems and workflows. **API access is currently in beta and available to approved users only.** ### Eligibility Accounts with **more than $100,000 in cumulative trading volume** are eligible to apply for API access. Meeting the eligibility requirement does not guarantee approval. Applications are reviewed individually based on TurboFlow’s current access criteria and technical availability. ### How to Apply To apply for API access, email [contacts@tf.xyz](mailto:contact@tf.xyz) and include: * Your TurboFlow UID * Your account email The TurboFlow team will review your application and follow up with eligible applicants. ### Important Notice API access is currently in beta. Availability, eligibility requirements, supported functionality, and access conditions may change as the program develops. For the latest information or API access enquiries, contact [contacts@tf.xyz](mailto:contact@tf.xyz) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://turboflow.gitbook.io/whitepaper/turboflow/professional-access/api-trading.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.