Flexible APIs for Modern Infrastructure
Access Gato's complete product ecosystem through a secure, high-performance API layer built to handle your most critical data workloads. Designed for rapid deployment and maximum uptime, our unified API endpoints give your developers the flexibility to build, test, and deploy custom solutions effortlessly.
API Offerings
Easy-to-use APIs to onboard new accounts, trade and manage your portfolio, customize fund transfer workflows and more.
Browse the full API documentation for REST, WebSocket, and FIX references.
Corporate Actions API
Manage dividends, stock splits, mergers, and other corporate action events across your portfolio.
View DocsRisk & Margin API
Monitor margin requirements, exposure limits, and real-time risk across accounts and positions.
View DocsPrefer to read the reference on this site? The Account Opening API reference is hosted here with full endpoint tables, alongside the rest of our API documentation.
Client SDKs
Native SDKs in C++, C#/.NET, and Python. Code in another language?
Simple JSON Samples
Trading scripts written in various languages so you can prototype in minutes — leveraging the simplicity of JSON.
Use Any Language: Samples for All Major Development Languages
Create your application in any language. No more C++/Java limitations. Use the technology you already know, and spend your time creating your application; not integrating.
import requests
url = "{BaseURI}/api/connect/token"
payload = {}
headers = {
'Authorization': 'Basic Og=='
}
response = requests.request(
"POST", url, headers=headers, data=payload
)
print(response.text)Building on the Gato APIs
The Gato developer platform exposes the same infrastructure our own applications run on: order routing and FIX session management, account opening and funding, journals and transfers, reference data, and real-time pre-trade risk. Nothing is a thin wrapper around a third party, so behaviour in your integration matches behaviour on the trading desk.
Integrations follow a predictable path. You provision scoped credentials for UAT, build against REST and WebSocket endpoints or a certified FIX session, run a conformance suite that exercises order lifecycle, cancel/replace, rejects, and recovery, then promote the same code to production with new keys. Risk limits, entitlements, and audit logging are enforced server-side, which means a client-side bug cannot route around a credit check or a restricted list.
Full endpoint references, request and response schemas, and SDK guides live in the documentation portal. The questions below cover what teams ask before they start.
What protocols do the Gato APIs support?
REST for account, funding, and reference-data workflows; WebSocket for streaming order state, positions, and market data; and FIX 4.2, 4.4, and 5.0 SP2 for order routing and drop-copy.
The same entitlements and risk checks apply regardless of the protocol you choose.
Which SDKs are available?
Native client SDKs in Python, C++, and C#/.NET wrap authentication, session management, reconnection, and sequence-number recovery, so teams can focus on trading logic instead of transport plumbing.
Is there a sandbox before production certification?
Yes. Every integration begins in a UAT environment with simulated venues and deterministic fills, followed by a conformance run against production-shaped sessions. Credentials, IP allow-lists, and rate limits are issued per environment.
How is API access secured?
API keys are scoped per environment and per entitlement, sessions are TLS-encrypted, and pre-trade risk controls are enforced server-side, so a compromised client cannot bypass credit, position, or restricted-list limits.
How are FIX sessions managed in production?
Session state, sequence-number recovery, reconnection, and per-session throttling are handled by the platform.
Client applications receive normalised order and execution events, so a venue reconnect or sequence gap does not become application logic each integrating team has to write and test itself.
What rate limits and quotas apply?
Limits are issued per environment and per credential, with separate ceilings for reference-data reads, order entry, and streaming subscriptions.
Throttled responses are explicit rather than silent, so clients can back off deterministically instead of guessing why messages were dropped.
How are breaking API changes handled?
Endpoints and FIX dictionaries are versioned, additive changes ship without a version bump, and breaking changes are published with a migration window and parallel availability so integrations can be cut over on their own schedule.
Contact Us
Have further questions? Reach out to our support team.