Gemini Developer Platform
Gemini is one developer platform for discovering markets, choosing an account, and integrating with supported trading products.
Account model note: Product access and account selection are interface-specific. Do not assume that one credential, account identifier, or selection method works across every product and protocol.
Start with your trading product
Choose what you want to trade before choosing a protocol.
- Spot crypto — current trading guides and API documentation.
- Margin — margin concepts and the current margin REST reference.
- Perpetuals — perpetuals concepts and the current derivatives REST reference.
- Prediction markets — event-contract guides and API documentation.
- Stocks — available in the Gemini UI. API trading and its developer documentation are coming soon.
Availability, eligibility, supported instruments, and interface coverage can differ by product, account, jurisdiction, and environment. Treat each product's documentation as the authority for those details.
Understand credentials and accounts
A credential authenticates a caller. An account identifies the context in which an operation occurs. Roles or OAuth scopes determine which operations the credential may perform. Product access is a separate concern and its cross-product model is still being standardized.
Current REST documentation describes two API-key patterns:
- A Master API key can target an account in its account group by including the account shortname where the operation supports it.
- An account-scoped API key is bound to one account.
OAuth, WebSocket, and FIX have their own authentication and account-selection behavior. Always follow the documentation for the interface and operation you are using.
Choose an interface
- REST APIs for request-and-response operations.
- WebSocket APIs for supported streaming and interactive workflows.
- FIX APIs for supported FIX sessions and messages.
- SDKs & Tools for the available MCP server, API samples, and agent skills. SDK packages and a dedicated Gemini API CLI are still in development.
For exact endpoint, stream, or message behavior, use the API Reference. Product guides explain when to use an interface; the reference remains the authority for how that interface behaves.
A safe integration flow
- Choose a trading product and confirm its availability for your use case.
- Create a credential supported by the interface.
- Identify the account that the operation will use.
- Confirm that the account has the required product access and the credential has the required role or scope.
- Discover the instrument and review product-specific mechanics.
- Preview the operation when the documented API supports a preview.
- Submit mutating operations only after surfacing the resolved account and intended action.
- Monitor the result through the documented status or event interface.
Use the demo environment where the product and operation are documented as supported.