exchange-rate-convert
Exchange Rate & Currency Conversion
Provides an API for real-time exchange rate lookups and currency conversion, allowing developers to easily integrate currency data into their business systems.
Usage Cost
2 coins/call
Quick Start
Use a unified response envelope and call directly from your backend.
https://openapi.toolkk.com/v1/exchange-rate-convertcURL Example
curl --request POST \
--url 'https://openapi.toolkk.com/v1/exchange-rate-convert' \
--header 'Content-Type: application/json' \
--header 'X-API-Key: YOUR_API_KEY' \
--data '{\n "fromCurrency": "USD",\n "toCurrency": "CNY",\n "amount": 100\n}'Python Example
import os
import requests
url = "https://openapi.toolkk.com/v1/exchange-rate-convert"
payload = {
"fromCurrency": "USD",
"toCurrency": "CNY",
"amount": 100
}
headers = {
"Content-Type": "application/json",
"X-API-Key": os.getenv("TOOLKK_API_KEY", "YOUR_API_KEY"),
}
response = requests.request("POST", url, headers=headers, json=payload, timeout=30)
response.raise_for_status()
print(response.json())Go Example
package main
import (
"bytes"
"fmt"
"io"
"net/http"
)
func main() {
endpoint := "https://openapi.toolkk.com/v1/exchange-rate-convert"
payload := []byte("{\n \"fromCurrency\": \"USD\",\n \"toCurrency\": \"CNY\",\n \"amount\": 100\n}")
req, err := http.NewRequest("POST", endpoint, bytes.NewBuffer(payload))
if err != nil {
panic(err)
}
req.Header.Set("Content-Type", "application/json")
req.Header.Set("X-API-Key", "YOUR_API_KEY")
resp, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
body, err := io.ReadAll(resp.Body)
if err != nil {
panic(err)
}
fmt.Println(string(body))
}Java Example
import java.net.URI;
import java.net.http.HttpClient;
import java.net.http.HttpRequest;
import java.net.http.HttpResponse;
public class ToolkkExample {
public static void main(String[] args) throws Exception {
String payload = "{\n \"fromCurrency\": \"USD\",\n \"toCurrency\": \"CNY\",\n \"amount\": 100\n}";
HttpRequest request = HttpRequest.newBuilder()
.uri(URI.create("https://openapi.toolkk.com/v1/exchange-rate-convert"))
.method("POST", HttpRequest.BodyPublishers.ofString(payload))
.header("Content-Type", "application/json")
.header("X-API-Key", "YOUR_API_KEY")
.build();
HttpResponse<String> response = HttpClient.newHttpClient()
.send(request, HttpResponse.BodyHandlers.ofString());
System.out.println(response.body());
}
}PHP Example
<?php
$endpoint = 'https://openapi.toolkk.com/v1/exchange-rate-convert';
$payload = "{\n \"fromCurrency\": \"USD\",\n \"toCurrency\": \"CNY\",\n \"amount\": 100\n}";
$ch = curl_init($endpoint);
curl_setopt_array($ch, [
CURLOPT_RETURNTRANSFER => true,
CURLOPT_CUSTOMREQUEST => 'POST',
CURLOPT_HTTPHEADER => [
'Content-Type: application/json',
'X-API-Key: YOUR_API_KEY',
],
CURLOPT_POSTFIELDS => $payload,
]);
$response = curl_exec($ch);
if ($response === false) {
throw new RuntimeException(curl_error($ch));
}
curl_close($ch);
echo $response;Response Example
{
"code": "SUCCESS",
"message": "success",
"data": {
"rate": 7.15,
"convertedAmount": 715,
"updatedAt": "2024-01-01 10:00:00"
}
}Examples illustrate the response structure. Actual results depend on the API response.
- Authentication
- Send X-API-Key in request headers
- Rate limit
- 600 req/min
- Timeout
- 10000 ms
Send your API Key in the X-API-Key header from your backend.
Check both HTTP status and business fields before treating a call as successful.
Use retries and backoff together with rate limits in high-frequency scenarios.
Request Fields
Send requests from your server with the key in the X-API-Key header.
Request Fields
The fields below are derived from example JSON for integration reference only.
| Path | Type | Required | Description | Sample |
|---|---|---|---|---|
| fromCurrency | string | Unspecified | Unspecified | USD |
| toCurrency | string | Unspecified | Unspecified | CNY |
| amount | number | Unspecified | Unspecified | 100 |
Request Example
{
"fromCurrency": "USD",
"toCurrency": "CNY",
"amount": 100
}- Authentication
- Send X-API-Key in request headers
- Rate limit
- 600 req/min
- Timeout
- 10000 ms
Response Fields
Examples illustrate the response structure. Actual results depend on the API response.
Response Fields
The fields below are derived from example JSON for integration reference only.
| Path | Type | Required | Description | Sample |
|---|---|---|---|---|
| code | string | Unspecified | Unspecified | SUCCESS |
| message | string | Unspecified | Unspecified | success |
| data | object | Unspecified | Unspecified | {...} |
| data.rate | number | Unspecified | Unspecified | 7.15 |
| data.convertedAmount | number | Unspecified | Unspecified | 715 |
| data.updatedAt | string | Unspecified | Unspecified | 2024-01-01 10:00:00 |
Response Example
{
"code": "SUCCESS",
"message": "success",
"data": {
"rate": 7.15,
"convertedAmount": 715,
"updatedAt": "2024-01-01 10:00:00"
}
}API overview
Capabilities, use cases, limitations, and frequently asked questions.
Exchange Rate & Currency Conversion API Overview
The Exchange Rate & Currency Conversion API helps developers quickly integrate currency lookups and conversion processing into their systems. It returns structured data, making it ideal for financial business integration, account reconciliation, and automated system integration.
Use Cases
- Integrate exchange rate and currency conversion capabilities into internal systems, SaaS platforms, automated workflows, or admin dashboards.
- Suitable for business scenarios requiring stable API calls, standardized responses, and orchestratable interfaces.
- We recommend implementing rate limiting, retry mechanisms, and result caching strategies to improve overall integration stability.
Integration Guidelines
- Verify request parameter formats, authentication methods, and error code handling logic before integration.
- For high-frequency query scenarios, ensure proper log tracking, timeout controls, and idempotency handling.
- If the results are used for risk control or automated decision-making, we recommend applying secondary validation based on your business rules rather than relying solely on the API response.