Conventions & Standards
Data types, currency formatting, precision resolution, and ISO standards used across the Depa API.
To ensure predictable behavior across international banking networks and distributed blockchains, Depa strictly adheres to global ISO standards.
1. Fiat Currency Amounts (ISO 80000-1)
Fiat monetary values are formatted according to ISO 80000-1 using a period (.) as the decimal separator and fixed 2-decimal precision.
Amounts in responses are strings
Responses return amounts as decimal strings (e.g. "100.50" instead of 100.50), which prevents floating-point rounding errors in JSON parsers. Request bodies take each amount in the type its endpoint documents in the API reference; parse response amounts with a decimal library rather than as floats.
{
"amount": "12500.50",
"currency": "EUR"
}2. Currency Codes (ISO 4217)
Currencies are identified using three-letter uppercase ISO 4217 codes. Depa supports accounts and execution across 23 global currencies:
EUR, USD, GBP, AED, AUD, CAD, CHF, CZK, DKK, HKD, HUF, JPY, KES, MXN, NOK, NZD, PLN, RON, SAR, SEK, SGD, TRY, ZAR.
Stablecoins (e.g., USDC, EURC, USDT) and native digital assets (e.g., ETH, BTC) follow standard market tickers.
3. Cryptocurrencies & Variable Resolution
Unlike traditional currencies that operate on cents (2 decimal places), blockchains utilize variable decimal precisions (e.g., 6 decimals for USDC, 8 for BTC, 18 for ETH).
Each trading pair has its own precision. GET /supported_pairs returns, for every pair, the
decimal places allowed on each side (base_resolution, quote_resolution) and the minimum order
size:
{
"data": [
{
"pair": "USDC/EUR",
"base_resolution": "6",
"quote_resolution": "2",
"min_volume": "10",
"min_amount": "10"
}
]
}4. Timestamps (POSIX Epoch)
Timestamps such as created_at and updated_at use Unix epoch time, in seconds since
1970-01-01T00:00:00Z (UTC):
{
"created_at": 1772813114,
"updated_at": 1772813120
}Two exceptions: payment link and quote expiry times (expires_at, valid_until) are ISO 8601
strings, and date filters such as start_date and end_date take YYYY-MM-DD.
5. Country Codes (ISO 3166-1 alpha-2)
National jurisdictions and nationality codes use two-letter uppercase ISO 3166-1 alpha-2 format:
| Code | Jurisdiction |
|---|---|
ES | Spain |
DE | Germany |
FR | France |
GB | United Kingdom |
US | United States |
SG | Singapore |
CH | Switzerland |
{
"country": "ES",
"nationality": "DE"
}