---
search:
  tags:
    - RFQs
    - POST
seo:
  description: >-
    Creates a request for quote, soliciting pricing from makers for one or more
    legs. Reference for the POST /rfqs endpoint in the REST API.
sidebar:
  label: Create an RFQ
  badge: POST
title: Create an RFQ
type: openapi-operation
---
Creates a request for quote, soliciting pricing from makers for one or more legs.

### Endpoint

- Method and path: `POST /rfqs`
- Operation ID: `createRfq`
- API reference: [POST /rfqs](/api-reference/rest/rfqs/create-rfq)
- Complete specification: [OpenAPI (YAML)](/openapi.yml)
- Spec location (JSON Pointer): `#/paths/~1rfqs/post`

#### Authorization

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

#### Parameters

```yaml
- $ref: "#/components/parameters/VersionHeader"
- $ref: "#/components/parameters/IdempotencyKeyHeader"
```


#### Request body

Required: yes

Content type: `application/json`

Schema:

```yaml
$ref: "#/components/schemas/CreateRfqRequest"
```

Example: Example

```json
{
  "client_rfq_id": "rfq-20260804-001",
  "ticker": "UDX-EXAMPLE-MARKET",
  "quantity": "100",
  "side": "buy"
}
```


#### Responses

##### `202`

The exchange accepted the RFQ for processing.

Headers:

```yaml
UDX-Version:
  $ref: "#/components/headers/VersionHeader"
UDX-Idempotent-Replayed:
  $ref: "#/components/headers/IdempotentReplayed"
```

Content type: `application/json`

Schema:

```yaml
$ref: "#/components/schemas/RfqSubmissionResponse"
```

Example: Example

```json
{
  "rfq": {
    "client_rfq_id": "rfq-20260804-001"
  }
}
```

##### `400`

The request was malformed or the exchange rejected the RFQ at submission.

Headers:

```yaml
UDX-Version:
  $ref: "#/components/headers/VersionHeader"
```

Content type: `application/problem+json`

Schema:

```yaml
$ref: "#/components/schemas/ProblemDetails"
```

Example: The exchange rejected the RFQ

```json
{
  "type": "urn:udx:problem:rfq-rejected",
  "title": "Bad Request",
  "status": 400,
  "detail": "RFQ rejected; it was not created",
  "instance": "urn:request-id:8f14e45f-ceea-4abc-a743-e89a34d3f6ef"
}
```

##### `401`

No valid credential was provided.

Headers:

```yaml
UDX-Version:
  $ref: "#/components/headers/VersionHeader"
```

Content type: `application/problem+json`

Schema:

```yaml
$ref: "#/components/schemas/ProblemDetails"
```

Example: Authentication failed

```json
{
  "type": "urn:udx:problem:invalid-authentication-credentials",
  "title": "Unauthorized",
  "status": 401,
  "detail": "invalid authentication credentials",
  "instance": "urn:request-id:8f14e45f-ceea-4abc-a743-e89a34d3f6ef"
}
```

##### `403`

The credential lacks the trade scope.

Headers:

```yaml
UDX-Version:
  $ref: "#/components/headers/VersionHeader"
```

Content type: `application/problem+json`

Schema:

```yaml
$ref: "#/components/schemas/ProblemDetails"
```

Example: Insufficient permissions

```json
{
  "type": "urn:udx:problem:insufficient-permissions",
  "title": "Forbidden",
  "status": 403,
  "detail": "insufficient permissions",
  "instance": "urn:request-id:8f14e45f-ceea-4abc-a743-e89a34d3f6ef"
}
```

##### `409`

This idempotency key is still in use, or its request completed with a response too large to replay. The problem type tells the two apart.

Headers:

```yaml
UDX-Version:
  $ref: "#/components/headers/VersionHeader"
```

Content type: `application/problem+json`

Schema:

```yaml
$ref: "#/components/schemas/ProblemDetails"
```

Example: First request still running

```json
{
  "type": "urn:udx:problem:request-with-header-in-progress",
  "title": "Conflict",
  "status": 409,
  "detail": "a request with this UDX-Idempotency-Key is already in progress",
  "instance": "urn:request-id:8f14e45f-ceea-4abc-a743-e89a34d3f6ef"
}
```

Example: Completed without a replayable response

```json
{
  "type": "urn:udx:problem:response-too-large-to-replay",
  "title": "Conflict",
  "status": 409,
  "detail": "this request already executed, but its response was too large to replay; do not resend it with a fresh UDX-Idempotency-Key, read the affected resource to confirm the result",
  "instance": "urn:request-id:8f14e45f-ceea-4abc-a743-e89a34d3f6ef"
}
```

##### `422`

This idempotency key belongs to a different request.

Headers:

```yaml
UDX-Version:
  $ref: "#/components/headers/VersionHeader"
```

Content type: `application/problem+json`

Schema:

```yaml
$ref: "#/components/schemas/ProblemDetails"
```

Example: Example

```json
{
  "type": "urn:udx:problem:header-used-for-different-request",
  "title": "Unprocessable Entity",
  "status": 422,
  "detail": "UDX-Idempotency-Key was already used for a different request",
  "instance": "urn:request-id:8f14e45f-ceea-4abc-a743-e89a34d3f6ef"
}
```

##### `429`

The member rate limit was exceeded.

Headers:

```yaml
UDX-Version:
  $ref: "#/components/headers/VersionHeader"
Retry-After:
  $ref: "#/components/headers/RetryAfter"
Cache-Control:
  $ref: "#/components/headers/NoStore"
```

Content type: `application/problem+json`

Schema:

```yaml
$ref: "#/components/schemas/ProblemDetails"
```

Example: Example

```json
{
  "type": "urn:udx:problem:member-rate-limit-exceeded",
  "title": "Too Many Requests",
  "status": 429,
  "detail": "this member has temporarily exceeded its request rate",
  "instance": "urn:request-id:8f14e45f-ceea-4abc-a743-e89a34d3f6ef"
}
```

##### `500`

Something went wrong on UDX's side.

Headers:

```yaml
UDX-Version:
  $ref: "#/components/headers/VersionHeader"
```

Content type: `application/problem+json`

Schema:

```yaml
$ref: "#/components/schemas/ProblemDetails"
```

Example: Internal server error

```json
{
  "type": "urn:udx:problem:internal-error",
  "title": "Internal Server Error",
  "status": 500,
  "detail": "internal error",
  "instance": "urn:request-id:8f14e45f-ceea-4abc-a743-e89a34d3f6ef"
}
```

##### `503`

Either request admission is temporarily unavailable, or the submission itself failed indeterminately: the exchange may or may not have received the RFQ.

Headers:

```yaml
UDX-Version:
  $ref: "#/components/headers/VersionHeader"
Cache-Control:
  $ref: "#/components/headers/NoStore"
Retry-After:
  $ref: "#/components/headers/RetryAfter"
```

Content type: `application/problem+json`

Schema:

```yaml
$ref: "#/components/schemas/ProblemDetails"
```

Example: The RFQ may or may not have been created

```json
{
  "type": "urn:udx:problem:rfq-outcome-unknown",
  "title": "Service Unavailable",
  "status": 503,
  "detail": "the RFQ may or may not have been created",
  "instance": "urn:request-id:8f14e45f-ceea-4abc-a743-e89a34d3f6ef"
}
```

Example: Admission temporarily unavailable

```json
{
  "type": "urn:udx:problem:request-admission-unavailable",
  "title": "Service Unavailable",
  "status": 503,
  "detail": "request admission is temporarily unavailable",
  "instance": "urn:request-id:8f14e45f-ceea-4abc-a743-e89a34d3f6ef"
}
```


#### Referenced definitions

The references in the excerpts above resolve to these definitions in the complete specification.

##### `#/components/schemas/CreateRfqRequest`

```yaml
type: object
description: The fields needed to create an RFQ.
required:
  - client_rfq_id
  - side
oneOf:
  - description: One single-leg or multi-leg market by ticker, sized in contracts.
    required:
      - ticker
      - quantity
  - description: One single-leg or multi-leg market by ticker, sized in dollars.
    required:
      - ticker
      - cash_quantity
  - description: An ad-hoc strategy by legs, sized in contracts.
    required:
      - legs
      - quantity
  - description: An ad-hoc strategy by legs, sized in dollars.
    required:
      - legs
      - cash_quantity
properties:
  client_rfq_id:
    $ref: "#/components/schemas/ClientId"
  ticker:
    type: string
    minLength: 1
    maxLength: 128
    description: Published single-leg or multi-leg market to request a quote for, identified by its ticker.
    example: UDX-EXAMPLE-MARKET
  legs:
    $ref: "#/components/schemas/RfqLegList"
  quantity:
    type: string
    pattern: ^[0-9]+(\.[0-9]{1,2})?$
    maxLength: 24
    description: Number of contracts to quote, as a whole number.
    example: "100"
  cash_quantity:
    type: string
    pattern: ^[0-9]+(\.[0-9]{1,6})?$
    maxLength: 24
    description: Size of the RFQ in dollars.
    example: "0.55"
  side:
    type: string
    enum:
      - buy
      - sell
    description: The side the customer wants to execute.
  account_id:
    type: string
    minLength: 1
    description: Account to create the RFQ under. Required for an unrestricted API key; an account-restricted key uses its bound account.
    example: "6820943174116859281"
```

##### `#/components/schemas/ClientId`

```yaml
type: string
description: A client-supplied correlation identifier.
example: client-20260804-001
```

##### `#/components/schemas/RfqLegList`

```yaml
type: array
minItems: 1
description: The component markets and opposing sides that define the RFQ strategy, in the order supplied.
items:
  $ref: "#/components/schemas/RfqLeg"
```

##### `#/components/schemas/RfqLeg`

```yaml
type: object
additionalProperties: false
description: A single component leg of an RFQ.
required:
  - ticker
properties:
  ticker:
    $ref: "#/components/schemas/Ticker"
  opposing_side:
    type: boolean
    default: false
    description: Whether this leg takes the side opposite the RFQ or the same side.
```

##### `#/components/schemas/Ticker`

```yaml
type: string
minLength: 1
maxLength: 128
description: A human-meaningful natural key naming a single-leg or multi-leg market.
example: UDX-EXAMPLE-MARKET
```

##### `#/components/headers/VersionHeader`

```yaml
description: API version used for this response.
schema:
  type: string
  maxLength: 10
  description: A dated API version (YYYY-MM-DD).
  example: 2026-07-15
```

##### `#/components/headers/IdempotentReplayed`

```yaml
description: true for a replayed response; omitted otherwise.
schema:
  type: string
  enum:
    - "true"
  description: Always the string true when present.
  example: "true"
```

##### `#/components/schemas/RfqSubmissionResponse`

```yaml
type: object
description: The exchange accepted the RFQ submission for processing.
required:
  - rfq
properties:
  rfq:
    $ref: "#/components/schemas/RfqSubmission"
```

##### `#/components/schemas/RfqSubmission`

```yaml
type: object
description: An accepted RFQ submission.
required:
  - client_rfq_id
properties:
  client_rfq_id:
    $ref: "#/components/schemas/ClientId"
```

##### `#/components/schemas/ProblemDetails`

```yaml
type: object
description: An RFC 9457 machine-readable error, returned on every non-2xx response. The response's Content-Language header identifies the language used by title and detail, and Vary includes Accept-Language.
required:
  - type
  - title
  - status
properties:
  type:
    type: string
    format: uri-reference
    maxLength: 2048
    description: A stable URN identifying the kind of problem, for example urn:udx:problem:insufficient-permissions. Branch on it rather than on the localized detail. It is an identifier, not a URL to dereference.
  title:
    type: string
    maxLength: 40
    example: Bad Request
    description: A localized, human-readable summary of the error category. Stable for a given status code and resolved language — clients must not use it as a machine-readable discriminator.
  status:
    type: integer
    example: 400
    description: The HTTP status code, repeated from the response itself.
  detail:
    type: string
    maxLength: 500
    example: malformed request body
    description: A localized, human-readable explanation specific to this occurrence. Clients must not parse it for machine-readable information.
  instance:
    type: string
    format: uri-reference
    maxLength: 100
    example: urn:request-id:8f14e45f-ceea-4abc-a743-e89a34d3f6ef
    description: An identifier for this specific occurrence, so it can be correlated with server-side logs if you need to report it.
```

##### `#/components/headers/RetryAfter`

```yaml
description: Whole seconds to wait before retrying.
schema:
  type: integer
  minimum: 1
  description: A positive delay in whole seconds.
  example: 2
```

##### `#/components/headers/NoStore`

```yaml
description: Prevents caching this response.
schema:
  type: string
  enum:
    - no-store
  description: Always the cache directive no-store.
  example: no-store
```

##### `#/components/parameters/VersionHeader`

```yaml
name: UDX-Version
in: header
required: false
description: Dated API version (YYYY-MM-DD).
schema:
  type: string
  minLength: 10
  maxLength: 10
  description: A dated API version (YYYY-MM-DD).
  example: 2026-07-15
```

##### `#/components/parameters/IdempotencyKeyHeader`

```yaml
name: UDX-Idempotency-Key
in: header
required: false
description: Optional client-generated key that makes a mutation safe to retry.
schema:
  type: string
  minLength: 1
  maxLength: 255
  description: A unique, client-generated key identifying this request.
  example: b6f1c2a4-2b7e-4c1a-9c2e-2d1f8a3e4b5c
```