> For the complete documentation index, see [llms.txt](https://developer.barchart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.barchart.com/getting-started/requesting-access.md). # Requesting Access How to request a trial or production access to Openfeed APIs Interested in accessing **Openfeed market data** for your applications, trading systems, or analytics platforms? Our team can help you evaluate the best way to integrate Openfeed into your environment. To get started, please complete our [**Contact Us form**](https://www.barchart.com/solutions/contact). You can also explore [Barchart's Institutional Solutions](https://www.barchart.com/solutions/services/stream) site or [Market Data Explorer](https://www.barchart.com/solutions/market-category/all-markets) to review its coverage. Once we receive your request, a Barchart **Data Consultant** will review your requirements and schedule a short working session to discuss your use case and recommend the most appropriate data access model. Providing a few details upfront helps us prepare a solution tailored to your needs. Helpful information includes: * **Use Case** – What are you building or analyzing with the data? (e.g., trading systems, analytics, research, client-facing tools) * **Application Access** – Is the application internal, client-facing, or subscription-based? Will users be able to download data? * **Historical Data Needs** – Do you require historical data for backtesting or research, or only real-time market data? These details allow our team to recommend the right **data coverage, connectivity model, and licensing structure** for your environment. After reviewing your request, we’ll schedule a **brief working session** to walk through your requirements and help you get started quickly with Openfeed. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://developer.barchart.com/getting-started/requesting-access.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 `automate deployments from our CI pipeline` 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.