Fundamentals
Multicloud / Geofence
API Examples
API Specification
SDKs / Codegen
Batch Processing
Best Practice
Error Codes
| Parameter | Required | Type | Default | Description |
|---|---|---|---|---|
| from-value | yes | string | The value to convert from (e.g. 10.95) | |
| from-type | yes | string | The type of the value to convert from (e.g. USD) | |
| to-type | yes | string | The type to convert to (e.g. EUR) | |
| historical-date | no | string | Convert using the rate on a historical date, accepted date formats are: YYYY-MM-DD, YYYY-MM, YYYY. Historical rates are stored with daily granularity so the date format YYYY-MM-DD is preferred for the highest precision. If an invalid date or a date too far into the past is supplied then the API will respond with 'valid' as false and an empty 'historical-date' |
| Parameter | Type | Description |
|---|---|---|
| valid | boolean | True if the conversion was successful and produced a valid result |
| result | string | The result of the conversion in string format |
| result-float | float | The result of the conversion as a floating-point number |
| from-value | string | The value being converted from |
| from-type | string | The type of the value being converted from |
| from-name | string | The full name of the type being converted from |
| from-symbol | string | The standard UTF-8 symbol used to represent the type being converted from |
| to-type | string | The type being converted to |
| to-name | string | The full name of the type being converted to |
| to-symbol | string | The standard UTF-8 symbol used to represent the type being converted to |
| historical-date | string | If a historical conversion was made using the 'historical-date' request option this will contain the exact date used for the conversion in ISO format: YYYY-MM-DD |
| Characteristic | Value | Description |
|---|---|---|
| Avg Latency | 15ms | Average RTT for requests within the same data center/region |
| Max Rate | 500/second | Maximum inbound request rate. Exceeding this will result in request throttling |
| Max Concurrency | 250 | Maximum concurrent/simultaneous requests. Exceeding this will result in error code 06 [TOO MANY CONNECTIONS] |