Introduction
The Coins API is a product extension of the Daya API. It adds digital-asset market data, balances, portfolio, transactions, quote-based trading, and crypto and fiat withdrawals to the same Daya account and the same API key you already use.Coins is not a separate platform with its own credentials. It uses your existing Daya API key with Coins scopes. If you already integrate the Daya API, you only add the Coins surface — nothing about your key issuance or auth changes.
What you can build
Trading experiences
Quote an asset pair, then accept the quote to place a buy or sell order.
Portfolio dashboards
Read consolidated balances, holdings, and 24h stats to render a portfolio view.
Funding flows
Surface supported crypto and fiat deposit options so customers can fund.
Treasury and payouts
Manage saved addresses and bank accounts, then create crypto or fiat withdrawals.
Base URL
All Coins endpoints are served under the Coins path of the Daya API:Authentication in one line
Send your Daya API key in theX-API-Key header. The key must carry the relevant Coins scope (coins:read, coins:trade, coins:write, or coins:withdraw). See Authentication.
Two quote types
Coins uses two separate, short-lived quotes. Each response returns anid; pass it back as quote_id to execute:
POST /quote— a trade quote between two coins assets. Execute it withPOST /orders.POST /fx/quotes— a USD→NGN conversion quote for cashing out. Execute it withPOST /fiat-withdrawals.
410 Gone, a reused one 409 Conflict. Trade-quote amounts are shown fee-inclusive; the taker fee settles as a separate component at execution.
The execution venue is an internal detail and is never part of the API contract. You request the economic result of a trade; Daya handles routing and settlement.
Next steps
Quickstart
Make your first authenticated Coins call end to end.
Authentication
The shared Daya API key model and Coins scopes.
Concepts
Balances, quotes, orders, transactions, and withdrawals.
API Reference
Every Coins endpoint, generated from the OpenAPI spec.