---
search:
  tags:
    - RFQs
    - GET
seo:
  description: >-
    Returns one RFQ visible to the caller's member by its exchange id — one the
    member raised,… Reference for the GET /rfqs/{rfq_id} endpoint in the REST
    API API.
sidebar:
  badge: GET
  label: Get an RFQ
title: Get an RFQ
type: openapi-operation
---
Returns one RFQ visible to the caller's member by its exchange id — one the member raised, or one soliciting quotes from it.

### Endpoint

- Method and path: `GET /rfqs/{rfq_id}`
- Operation ID: `getRfq`
- API reference: [GET /rfqs/{rfq_id}](/api-reference/rfqs/getrfq)

#### Authorization

- Accepted credentials: `UDX-Access-Key` header and `UDX-Access-Timestamp` header and `UDX-Access-Signature` header; or Bearer token in `Authorization`
- Details: [Authentication](/authentication)

#### Parameters

- `UDX-Version` (`header`) — Dated API version (YYYY-MM-DD). Omit to use the oldest supported version. An unknown version returns `400`.
- `rfq_id` (`path`, required) — Exchange-assigned RFQ identifier.

#### Responses

- `200` — The requested RFQ.
- `401` — No valid credential was provided.
- `403` — The credential lacks the `read` scope.
- `404` — The requested resource doesn't exist or isn't visible to the caller.
- `429` — The member rate limit was exceeded. Wait for `Retry-After`.
- `500` — Something went wrong on UDX's side.
- `503` — Request admission is unavailable. Retry later.