Money, time zones and limits
Supported currencies: MDL, RON, EUR, USD, GBP, UAH, PLN, TRY, CHF, RUB, GEL, KZT. All have two minor-unit decimals: 10000 means 100.00. Send integer money amounts; do not use floating-point rounding.
New operations use the current company currency. Reservations and API refunds retain their recorded currency. Changing company currency relabels existing amounts without FX conversion. The data ledger also exposes recorded_currency when available.
Send RFC3339 timestamps with an offset; UTC Z is recommended. Convert local dates using the business/location IANA time zone and explicitly resolve daylight-saving ambiguity. Never assume the server or browser time zone.
| Limit | Value |
|---|---|
| Requests per connection | 120/minute, shared across API calls. |
| Requests per IP | 300/minute per group: configuration, datasets, financial operations. |
| Page | 50 results by default, at most 100. |
| JSON body | At most 100000 bytes. |
| Financial values | 0–100000000 minor units; some operations require a positive amount. |
| Connections | At most 20 active connections and 10 authorized locations per connection. |
| Key | No expiry by default, or an optional 1–365 day term. |
| Configuration / dataset cursor | 1 hour / 7 days. |
| Quote / unstarted reservation | 120 seconds / 10 minutes. |
Financial command results are retained. Preview replay is retained for at least 24 hours and never extends the quote. Key validity, revocation, expiry, scopes and authorized bindings are checked again on replay.
On 429, honor Retry-After. Increase the polling interval when there are no changes. Never log Authorization, card codes, customer identifiers or complete financial payloads.