Submit and poll for FX Quotes
The “Request a Quote” operation allows developers to submit an asynchronous Request for Quote (RFQ) for foreign exchange (FX) transactions through the ANZ Fileactive FX RFQ Pricing Service. This API call initiates the quote process by submitting FX trade parameters, enabling users to receive a quote for a specific currency pair.
Key Points:
- Endpoint: Submit requests to the
/fx/v1.0/quotes/{country-code}
endpoint. - Method:
POST
- authorisation: Requires a valid bearer token obtained via OAuth 2.0, included in the
authorisation
header asBearer <access_token>
. - Headers:
X-Correlation-Id
(optional): A unique identifier for tracking requests across services.X-Message-Id
(required): A unique identifier for duplicate checks and traceability.
- Request Body: The request body should be in JSON format and include details such as:
customerExternalIdentifier
(string): A customer-specific identifier used for internal tracking.channelTransactionIdentifier
(string, required): A unique identifier for the quote request, provided by the initiating channel.currencyPair
(string): The currency pair for which the quote is requested (e.g., “AUD/USD”).requestLegs
(array, required): Specifies the details of the FX trade legs.
Example Request:
POST /fx/v1.0/quotes/NZ HTTP/1.1
Host: api.fileactive.anzgcis.com
authorisation: Bearer <access_token>
Content-Type: application/json
X-Message-Id: 71d6fb19-7515-40dc-b045-e17550b67600
{
"customerExternalIdentifier": "CRN0000000001",
"channelTransactionIdentifier": "0123456789",
"currencyPair": "AUD/USD",
"requestLegs": [
{
// Request leg details
}
]
}
Example Response:
On success, the service will acknowledge the quote request with a 202 Accepted
status, and a unique quote identifier will be issued for tracking.
{
"channelTransactionIdentifier": "0123456789",
"quoteIdentifier": "MKT-d75a03b5-2d7c-4db0-b30f-bcccc67a4fed",
"status": "ACCEPTED"
}
Usage Notes:
- Tracking: Use the
quoteIdentifier
from the response to track the status of the RFQ and for any further actions, such as polling for the response or accepting the quote. - Error Handling: Ensure to handle common HTTP errors such as:
- 400 Bad Request: Malformed requests.
- 401 Unauthorised: Missing or invalid tokens.
- 503 Service Unavailable: If the service is down.