# APIs There are several ways to programmatically interact with [The Premia Protocol](/what-is-premia.md#the-premia-protocol). In this section we will specifically be talking about access via an API. Currently we have 3 major APIs set up. Please take note which ones are more applicable for developers, and which ones are more applicable for traders. ### [Orderbook API](#orderbook-api) Direct use of the Orderbook API is suggested for *advanced* web3 developers (ie aggregator protocols), not traders. For a more trader centric API, please have a look at our [Containerized API](#containerized-api) solution. The orderbook API is useful for *direct* access to the orderbook and its current state. It will require additional knowledge of web3 functionality and formatting as there are many aspects of the lifecycle of option trading that will require direct interaction with our on-chain smart contracts. ### [Subgraph API](#subgraph-api) Like the orderbook API, this is for advanced web3 developers. Advanced data querying can be done via our Subgraph API. This is useful for data science, dashboards, and other data centric projects. ### [Containerized API](#containerized-api) The containerized API is an "all-in-one" solution for users who would like to programmatically trade (in any coding language) using the orderbook, but do not want to be slowed down with "Defi integration" (aka web3). This API solution is very similar to using a centralized exchange API, but with all the benefits of interacting with a decentralized exchange. --- # Agent Instructions: 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 current page URL with the `ask` query parameter: ``` GET https://docs.premia.blue/developer-center/apis.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.