# Request quote Send a quote request to receive firm quotes from liquidity providers for the specified symbol, tenor, amount, and direction (bid, ask, two-way) for a given price type. After the initial success response , you must query the status of your request to receive the latest quotes and status (see Query quote request (server ID) and Query quote request (client ID)). When you receive a quote, you can then accept it (Accept quote). Endpoint: POST /v2/rfs Version: 1.0.1 Security: SSO_TOKEN ## Request fields (application/json): - `clOrderId` (string, required) Request reference ID assigned by you. - `symbol` (string, required) Base and term currency separated by a slash (for example ). - `amount` (number, required) - Spot, outright, NDF: dealt amount. - Swap: near leg dealt amount. - `dealtCurrency` (string, required) Dealt currency. Must one of the instruments in . - `expiry` (integer, required) The definition of this property depends on the property ([rfq](#rfsrfq/quoterequest/t=request&path=rfq)): * or not included (RFS workflow) Request expiry time in seconds when the request is received.\ The expiration also depends on the server expiry configuration. Typical expiration time is 120 seconds.\ If the value of this parameter is greater than configured on the server, the server value is used. * (RFQ workflow) Duration time in seconds for a single quote. Minimum 30 seconds. Maximum 86400 seconds (24 hours). This value must match exactly the value configured on the server.\ The server must be configured to enable the RFQ workflow. Please contact your Technical Account Manager to discuss settings. - `rfq` (boolean) Quote workflow of the request: * Not included or =RFS workflow: request a stream of quotes. The ([expiry](#rfsrfq/quoterequest/t=request&path=expiry)) property specifies the expiry time of the request. * =RFQ workflow: request a single quote that is valid for a duration specified by the ([expiry](#rfsrfq/quoterequest/t=request&path=expiry)) property. The server must be configured to enable the RFQ workflow. Please contact your Technical Account Manager to discuss settings. - `nearValueDate` (string, required) Tenor or broken date in the format - Spot, outright: value date. - Swap: near leg value date. - NDF: value date if not specified. - `farDealtAmount` (number) Far leg dealt amount. - `farValueDate` (string) Tenor or broken date in the format . - Swap, fwd/fwd: far leg value date. - NDF swap: value date required if not specified. - `fixingDate` (string) NDF fixing date, tenor or broken date in the format . Required if not specified. - `farFixingDate` (string) NDF swap far leg fixing date, tenor or broken date in the format . Required if not specified. - `side` (string, required) , , or from the requester’s perspective and always for the dealt currency. - `priceType` (string, required) - - - - - - - `customerAccount` (string, required) ID of the legal entity for which quote request is being executed. - `customerOrg` (string, required) ID of the organization for which quote request is being executed. - `priceViewType` (integer) Whether quotes from all liquidity providers are collected into a single response (recommended) or each provider quote is sent as separate response: * 1=quotes collected into a single response (recommended). * 0 or any positive integer=non aggregated view, each liquidity-provider quote is sent as a separate response. - `depth` (integer) Requested depth-of-book starting with the top of the book. For example, if set to 5, you receive a maximum of 5 quotes on each side (buy/sell) is 5 as long as providers respond with 5 or more quotes. - `providers` (array) List of provider IDs to receive the request. If not specified, the server sends the request to all eligible providers. - `customParameters` (object) Collection of parameters that are unique to your organization. The number of parameters, their keynames, and values are defined by you. Contact your Integral Technical Account Manager to enable and configure custom parameters. Your custom parameters are included in API responses and in STP trade download. Custom parameters sent to Integral via API are stored in the database directly. No validation is performed. The maximum size of the property is characters, including all keys, values, and JSON syntax characters. - `customParameters.keyName` (string) The keyname of a custom parameter key/value pair as defined by your organization. Contact your Integral Technical Account Manager to enable and configure custom parameters. - `customParameters.value` (string) The value of a custom parameter key/value pair as defined by your organization. Contact your Integral Technical Account Manager to enable and configure custom parameters. ## Response 202 fields (application/json): - `requestId` (string) ID assigned to your request by the server. Use this ID to accept a quote. You need to use this ID or your ID to query your request to get quotes and status. - `clOrderId` (string) ID assigned by you from your request. You need to use this ID or the server ID to query your request to get quotes and status. - `event` (string) Indicates the request is received for processing. You need to query your request for get quotes and status of your request. ## Response 400 fields (application/json): - `message` (string) The validation error reason code. See [Reason codes](#section/Reason-codes) for the list of codes.