Authentication

Live only for now. Coins does not have a sandbox yet — every request runs against the live environment with real balances and real money. Sandbox keys (sk_sandbox_...) are not accepted, and the dashboard’s sandbox mode shows a notice instead of Coins data. Sandbox support is on the way.

The shared key model

Coins is an extension of the Daya API, so it does not have its own key-issuance flow. You authenticate Coins requests with the same Daya API key you use for the rest of the Daya API — the same key, the same header, the same dashboard.

Issue and manage your Daya API keys in the Daya dashboard. When you create or edit a key, grant it the Coins scopes your integration needs. There is no separate Coins key to request.

Send the key in the X-API-Key header on every request:

X-API-Key: YOUR_DAYA_API_KEY

Coins scopes

A Daya API key carries scopes. To call Coins endpoints, the key must include the matching Coins scope:

Scope	Grants
`coins:read`	Assets, prices, markets, balance, portfolio, transactions, deposit options, and withdrawal information
`coins:trade`	Request quotes (`/quote`, `/fx/quotes`) and place orders (`/orders`)
`coins:write`	Manage bank accounts and saved withdrawal addresses
`coins:withdraw`	Create crypto and fiat withdrawals

coins:withdraw authorizes fund movement off the platform. Only attach it to keys stored in trusted server-side systems.

Making an authenticated request

curl --request GET \
  --url https://api.daya.co/coins/v1/balance \
  --header 'X-API-Key: YOUR_DAYA_API_KEY'

const response = await fetch('https://api.daya.co/coins/v1/balance', {
  headers: { 'X-API-Key': 'YOUR_DAYA_API_KEY' }
});

const result = await response.json();
console.log(result.data);

import requests

response = requests.get(
    'https://api.daya.co/coins/v1/balance',
    headers={'X-API-Key': 'YOUR_DAYA_API_KEY'}
)
print(response.json()['data'])

Error responses

Coins uses the standard Daya response envelope: { success, message?, data?, error?, timestamp }.

401 Unauthorized

Missing or invalid API key:

{
  "success": false,
  "message": "Unauthorized",
  "error": { "code": "API_KEY_INVALID", "message": "Invalid or missing API key" },
  "timestamp": "2026-01-15T10:30:00Z"
}

403 Forbidden

The key is valid but is missing the required Coins scope:

{
  "success": false,
  "message": "Forbidden",
  "error": { "code": "API_KEY_INVALID_SCOPE", "message": "Insufficient scope for this operation" },
  "timestamp": "2026-01-15T10:30:00Z"
}

Getting Started

Concepts

API Reference

Market Data

Account

Trading

Transactions

Deposits

Crypto Withdrawals

Fiat Withdrawals

Webhooks

The shared key model

Coins scopes

Making an authenticated request

Error responses

401 Unauthorized

403 Forbidden

Next steps

Quickstart

Concepts

​The shared key model

​Coins scopes

​Making an authenticated request

​Error responses

​401 Unauthorized

​403 Forbidden

​Next steps

Quickstart

Concepts

The shared key model

Coins scopes

Making an authenticated request

Error responses

401 Unauthorized

403 Forbidden

Next steps