Coinigy API
Agent-ready OpenAPI document · curated by JenticFinanceBankingapiKey27 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Place trades, manage alerts, and consolidate balances across multiple linked cryptocurrency exchanges through one Coinigy account.
Use for: Get my consolidated balances across all linked exchanges, Place a buy order on a specific exchange-market pair through Coinigy, Cancel an open order I placed via Coinigy, Set up a price alert for BTC-USD at a target price
Not supported: Does not handle KYC, fiat on-ramps, or custody - use for multi-exchange order placement, balances, alerts, and market data only.
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.
Install Jentic One Beta
Connect the Coinigy API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Coinigy API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcoinigy.com%2Fcoinigy" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcoinigy.com%2Fcoinigy" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Coinigy API.
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
Patterns agents use Coinigy API for, with concrete tasks.
★ 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.
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.
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.
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.
Through Jentic, list all linked exchanges, then return current balances and any open alerts
Key Endpoints
27 endpoints — jentic publishes the only available openapi specification for coinigy api, keeping it validated and agent-ready.
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
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
Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Coinigy API through Jentic.
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.
GET STARTED