Create a new FX spread rule
Create a new FX spread rule with configurable bid/ask spreads
/v2/fx/spreadsRequest Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Request payload for creating or updating a spread rule
Response Body
application/json
curl -X POST "https://example.com/v2/fx/spreads" \ -H "Content-Type: application/json" \ -d '{ "bid_spread_bps": 50, "ask_spread_bps": 50 }'{
"id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
"fx_tariff_id": "f12d958c-c80c-4752-862c-9e0c09506488",
"provider": "string",
"base_currency": "string",
"target_currency": "string",
"rate_type": "BUY",
"bid_spread_bps": 0,
"ask_spread_bps": 0,
"effective_from": "2019-08-24T14:15:22Z",
"effective_to": "2019-08-24T14:15:22Z",
"reason": "string",
"active": true,
"created_at": "2019-08-24T14:15:22Z",
"created_by": "ee824cad-d7a6-4f48-87dc-e8461a9201c4",
"modified_at": "2019-08-24T14:15:22Z",
"modified_by": "e8d4374d-93a1-4e98-a6c6-fdcf00c5059f"
}Previous Page
Convert an amount between currencies. Only `amount` is strictly required — all other parameters fall back to operator-configured AppConfig defaults when omitted. Tariff is resolved via a four-step chain: fx_tariff_id query param → customer's assigned tariff (when customer_id provided) → convert.default_tariff_id AppConfig → the active tariff marked is_default = TRUE. FX date resolution is owned by the FX module business-date lookup policy, so omitted dates anchor to the current business date and optional lookback may resolve the most recent stored rate within the configured prior calendar-day window.