FX Trade RFQ API
FX Trade RFQ API
Introduction
The FX Trade RFQ API provides a streamlined mechanism for obtaining FX quotes and executing trades against those quotes. It is built to meet the needs of financial systems and institutions that require accurate and timely trade execution in the foreign exchange market
Use Cases and Features
Quote Request
Users can request a foreign exchange quote by submitting a request with specific parameters such as currency pair, amount, currency amount, amount side, maturity date or tenor. This allows clients to obtain a firm, executable quote before committing to a trade.
Trade Execution Using Quote
Once a quote is obtained, users can execute a trade using the returned Quote ID. This ensures that the trade is executed at the exact terms agreed upon during the quoting phase, providing price certainty and reducing execution risk.
Detailed Quote Information
Upon a successful quote request, users receive comprehensive quote details including the Quote ID, buy/sell currency amounts, spot price and maturity date. These details are essential for pre-trade validation, audit trails, and reporting purposes.
Error Handling
The API provides detailed and structured error responses for both the quote and execution endpoints, helping users identify and understand issues with their requests, such as invalid currency pairs, missing parameters, or upstream provider failures, and take appropriate corrective action.
Markets
The FX Trade RFQ API is designed to support foreign exchange trading by enabling clients to request quotes and execute trades across multiple currency pairs. It provides a reliable and efficient mechanism for premium users who require accurate trade execution as part of their FX trading workflows.
Getting Started
To begin using the FX Trade RFQ API, you must complete the onboarding process through the External API Platform. Post successful onboarding, you will gain access to all Premium APIs provided by Danske Bank.
For detailed onboarding instructions, please visit the Danske Bank Open Banking Developer Portal
Environment Description
As described in the External API Platform onboarding guidelines, the FX Trade RFQ API will be available in two environments:
-
Sandbox: This environment is designed for initial integration tests and will provide mocked data. Users can execute trades with simulated parameters, allowing exploration of various functionalities without impacting real transactions.
-
Production: This environment provides access to real trade execution capabilities. Users can execute actual trades based on the parameters specified in their requests, with results reflecting the live trading environment.
Sandbox URLs
- Token Endpoint: https://sandbox-api.danskebank.com/sandbox-corporate/api/dk/business/oauth2/token
- FX Trade RFQ API: TBD (populate actual URL)
Production URLs
- Token Endpoint: https://api.danskebank.com/corporate/api/dk/business/oauth2/token
- FX Trade RFQ API: TBD (populate actual URL)
Authentication
To access a resource, the client must first request Client Credentials Grant token by calling the token endpoint specified in the OpenId configuration (token_endpoint). The request should be an x-www-form-urlencoded POST with the following parameters:
grant_type-client_credentials(read more).scope- should include a scope the client has access to for FX RFQ API usage (read more).client_id- the ID received after onboarding (read more).
Example Request:
curl --location --request POST 'https://example.com/oauth2/token' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'grant_type=client_credentials' \
--data-urlencode 'client_id=1233456' \
--data-urlencode 'scope=accounts'
Example Response:
{
"token_type": "Bearer",
"access_token": "A****",
"metadata": "m:",
"expires_in": 3600,
"consented_on": 1588933990,
"scope": "accounts"
}
Using the Access Token:
The access_token received is valid for 1 hour and must be included in the request header on all subsequent API requests:
Authorization: Bearer <access_token>
Supported Endpoints
| Endpoint | Method | Description |
|---|---|---|
/v1/rfq-service/quote | POST | Requests quote for currency pair |
/v1/rfq-service/trade | POST | Executes the trade upon user acceptance |
Implementation Details
Request Parameters
POST /rfq-service/quote
Executes a trade based on provided parameters.
| Parameter | Required | Description | Validations |
|---|---|---|---|
counterpart | Yes | Unique identifier of the counterparty requesting the quote. | Must be a valid string |
currencyPair | Yes | Currency pair for the FX quote, expressed as the base currency followed by the quote currency. | Must be a valid six-character currency pair using ISO 4217 currency codes, for example EURDKK. |
amountCcy | Yes | Currency in which the trade amount is specified. | Must be a valid ISO 4217 currency code, for example DKK. |
amount | Yes | Trade amount for which the quote is requested. | Must be a positive number. |
amountSide | Yes | Indicates whether the specified amount is being bought or sold. | Must be either BUY or SELL. |
maturityDate | Required if tenor is not provided | Requested maturity date of the trade. | Must be a valid date in YYYY-MM-DD format. |
tenor | Required if maturityDate is not provided. Ignored if maturityDate is supplied. | Standard tenor defining the period from the value date, or spot date, to the maturity date of the FX contract. | Must be a supported tenor value, for example ON, SP or 1W. |
Example Request
curl --location --request POST 'https://svc-fx-execution-shfd.apps.az3-osp00.danskenet.net/v1/rfq-service/quote' \
--header 'X-Authorization-Session: eyJhbGciOiJSUvghjkdfghjkllll4d&jjjkkfdgjW9tz2zLebbHP8kaA' \
--header 'Authorization: Bearer eyJ0eXAiOiJKV1QiLCJiGxtYnq92Ju68CLM61nqS0fSA4rOw' \
--data-raw '{
"counterpart": "DBDEMO1",
"currencyPair": "EURDKK",
"amountCcy": "DKK",
"amount": 1000000,
"amountSide": "BUY",
"maturityDate": "2026-08-31",
"tenor": null
}'
POST /rfq-service/trade
Executes a trade based on a previously obtained quote.
| Parameter | Required | Description | Validations |
|---|---|---|---|
quoteId | Yes | Unique identifier of the quote obtained from the /quote endpoint. | Must be a valid non-empty string. |
comment | No | Additional comments. | Must be a valid string. |
Example Request
curl --location --request POST 'https://svc-fx-execution-shfd.apps.az3-osp00.danskenet.net/v1/rfq-service/trade' \
--header 'X-Authorization-Session: eyJhbGciOiJSUvghjkdfghjkllll4d&jjjkkfdgjW9tz2zLebbHP8kaA' \
--header 'Authorization: Bearer eyJ0eXAiOiJKV1QiLCJiGxtYnq92Ju68CLM61nqS0fSA4rOw' \
--data-raw '{
"quoteId": "Q123456789",
"comment": "Executing against quoted rate"
}'
Response Parameters
POST /rfq-service/quote
Response parameters:
| Parameter | Description |
|---|---|
id | Unique identifier for the quote. Must be used for trade execution. |
spotRate | Spot price at the time of execution. |
forwardRate | Forward price at the time of execution. |
allInRate | The total all-in rate |
sold | Amount sold (includes currency and amount). |
bought | Amount bought (includes currency and amount). |
settleOn | The date on which the underlying transaction settles |
Response body:
{
"id": "BAOCDBBGHAONHYIVQAA1__KMAANBA",
"spotRate": 7.46942,
"forwardRate": -0.0115406,
"allInRate": 7.4578794,
"bought": {
"currency": "DKK",
"amount": 1000000
},
"sold": {
"currency": "EUR",
"amount": 134086.37
},
"settleOn": "2026-08-31"
}
POST /rfq-service/trade
Response parameters:
| Parameter | Description |
|---|---|
tradeId | Unique identifier of the executed trade. |
executionId | Unique identifier for the execution. |
counterpart | Counterpart identifier for the trade. |
bought | Amount bought (includes currency and amount). |
sold | Amount sold (includes currency and amount). |
maturityDate | Maturity date of the trade. |
product | Product type of the executed trade. |
tradeTime | Date and time when the trade was executed. |
spotPrice | Spot price at the time of execution. |
forwardPrice | Forward price at the time of execution. |
allInPrice | Total price including fees. |
autoSettle | Indicates whether the trade will auto-settle. |
comment | Any additional comments related to the trade. |
Response body:
{
"tradeId": "string",
"executionId": "string",
"counterpart": "string",
"bought": {
"currency": "EUR",
"amount": 1000000.0
},
"sold": {
"currency": "DKK",
"amount": 7450000.0
},
"maturityDate": "2026-08-31",
"product": "string",
"tradeTime": "2026-08-31T10:28:30.946Z",
"spotPrice": 7.45,
"forwardPrice": 7.46,
"allInPrice": 7.46,
"autoSettle": true,
"comment": "string"
}
API Response
The FX Trade RFQ API uses standardized HTTP status codes to indicate the success or failure of API requests.
| Status Code | Description | Resolution Steps |
|---|---|---|
200 OK | The request was successful. | No action needed. |
400 Bad Request | The request could not be understood or was missing required parameters. | Check the request syntax and ensure all required parameters are included. |
401 Unauthorized | Missing or incorrect authentication credentials. | Verify that authentication credentials are correct and included in the request. |
403 Forbidden | The request was understood, but it has been refused or access is not allowed. | Ensure that you have the necessary permissions to access the requested resource. |
404 Not Found | The requested resource could not be found. | Verify the resource URL and ensure that the resource exists. |
500 Internal Server Error | An error occurred on the server. | Try the request again later and contact support if the issue persists. |
Error Response Structure
{
"exceptionType": "",
"status": "",
"details": ""
}
Pricing
During the pilot phase, the API will be offered at no cost to selected customers. Final pricing details will be announced at a later date.
Architectural constraints
- State
- Active
Technical constraints
- Static URL
- /premium-apis/fx-trade-rfq-api
- Environment(s)
- PROD, SANDBOX
Is this helpful?