canonical: https://jentic.com/apis/coinigy.com/coinigy # Coinigy API Jentic publishes the only available OpenAPI specification for Coinigy API, keeping it validated and agent-ready. Coinigy is a multi-exchange cryptocurrency trading and portfolio management platform - the API exposes consolidated balances across linked exchange accounts, exchange-aware order placement and cancellation, price alerts, watchlists, and market data. Traders use it to manage positions across many exchanges from a single integration. ## For AI agents Place trades, manage alerts, and consolidate balances across multiple linked cryptocurrency exchanges through one Coinigy account. ## Scope Does not handle KYC, fiat on-ramps, or custody - use for multi-exchange order placement, balances, alerts, and market data only. ## Capabilities - Look up balances and balance history across all linked exchange accounts - Place and cancel orders on linked exchanges via Coinigy's unified order endpoint - Create, list, and delete price alerts on chosen markets - Manage exchange API keys attached to the Coinigy account - Browse exchanges, markets, tickers, and unified market data - Maintain watchlists and personalised user preferences - Pull aggregated activity feeds and crypto news ## Use cases ### Multi-Exchange Portfolio Consolidation Aggregate balances and trade history across many exchanges in a single Coinigy account, then expose them through one API. The balances and balanceHistory endpoints return consolidated views without per-exchange integration. Useful for traders running strategies across venues and accountants reconciling crypto holdings. Example prompt: Call POST /balances and return total holdings per asset summed across all linked exchanges ### Cross-Exchange Trade Execution Submit and cancel orders on any linked exchange through Coinigy's unified order endpoints, removing the need to integrate each exchange API individually. Suitable for trading dashboards and bots that operate across multiple venues with a single signed request flow. Example prompt: Submit a limit order via POST /addOrder for a chosen exchange-market pair and return the resulting order id ### Price Alerting and Market Monitoring Set price alerts on any supported market and receive a notification when triggered. Combine with the ticker and market data endpoints to build a watchlist-driven monitoring tool. Useful for active traders who watch many pairs at once. Example prompt: Create a price alert via POST /addAlert for BTC-USD at a target price and return the alert id ### AI Trading Assistant via Jentic Build an AI assistant that manages a multi-exchange Coinigy account through Jentic. The agent expresses an intent (rebalance, place an order, set an alert); Jentic resolves the right Coinigy operation, validates parameters, and executes with stored credentials so signing and key management stay outside the agent context. Example prompt: Through Jentic, list all linked exchanges, then return current balances and any open alerts ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/balances` | Get consolidated balances across linked exchanges | | POST | `/addOrder` | Place an order on a linked exchange | | POST | `/cancelOrder` | Cancel an open order | | POST | `/addAlert` | Create a price alert on a market | | POST | `/exchanges` | List supported exchanges | | POST | `/markets` | List markets across exchanges | | POST | `/ticker` | Get the current ticker for a market | ## Key resources - **User** — User info, preferences, and activity feed - **Accounts and Balances** — Linked exchange accounts plus consolidated balances and history - **Orders** — Place, list, and cancel orders across linked exchanges - **Alerts** — Create, list, and delete price alerts - **Exchanges and Markets** — Browse exchanges, markets, tickers, and market data - **API Keys** — Add, delete, and activate exchange API keys - **News and Watchlists** — Crypto news feed and user watchlists ## Why Jentic - **Setup:** Wiring Coinigy by hand means sending both its X-API-KEY and X-API-SECRET headers, handling the POST-based request style, and managing rate limits across multi-exchange order, balance, and alert endpoints yourself. Through Jentic you install once, import Coinigy from the API Directory, store the key and secret once, and your agent calls it. - **Permission scoping:** Coinigy takes the exchange and order target in the request body, so you scope by operations: limit the agent to the calls it needs, such as reading balances or a ticker, so operations like placing or cancelling an order are not included unless you add them. - **Credential handling:** Your Coinigy API key and secret are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'place an order on a linked exchange' or 'read exchange balances', and Jentic returns the matching Coinigy operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Binance API** — Direct exchange API for trading on Binance only - **Kraken API** — Direct exchange API for trading on Kraken only - **CoinGecko API** — Cross-exchange reference price and market data ## FAQ ### Why is there no official OpenAPI spec for Coinigy API? Coinigy publishes textual API documentation but not a machine-readable OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Coinigy API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Coinigy API use? Coinigy requires both an API key and an API secret, sent as the X-API-KEY and X-API-SECRET headers respectively. Through Jentic, both values are stored encrypted in the vault and the agent receives a scoped execution token rather than the raw credentials. ### Can I place orders on a specific exchange through Coinigy? Yes. POST /addOrder accepts an exchange code, market name, order type, price, and quantity, routing the order to the linked exchange account. POST /cancelOrder cancels an open order by its Coinigy order id. ### What are the rate limits for the Coinigy API? Coinigy enforces per-account request limits that vary by plan tier. The OpenAPI spec does not declare exact thresholds; check your Coinigy account dashboard for current per-minute and per-day limits. ### How do I create a price alert on Coinigy through Jentic? Install the SDK with pip install jentic, search Jentic for create a crypto price alert, load the schema for POST /addAlert, and execute with the exchange code, market, target price, and direction (above/below). ### Does Coinigy support consolidated balance history across linked exchanges? Yes. POST /balanceHistory returns balance series across all linked exchange accounts so you can chart portfolio value over time without integrating each exchange individually. ### Can I limit what my agent is allowed to do with the Coinigy API? Yes. Because Jentic One is self-hosted, you decide which Coinigy operations your agent may call, and Coinigy takes the exchange and order target in the request body, so you scope purely by operation. You can allow read-only calls such as POST /balances, POST /balanceHistory, or POST /ticker while withholding POST /addOrder and POST /cancelOrder, so the agent cannot place or cancel trades unless you add those operations. Your API key and secret stay with your own instance and are injected only for the operations you have permitted.