---
title: "Delete RFQ"
method: DELETE
path: "/rfqs/{rfq_id}"
tags: ["Rfqs"]
---

# Delete RFQ

`DELETE /rfqs/{rfq_id}`

Queues cancellation of an RFQ.

Cancellation is asynchronous. Subscribe to the private WebSocket channel
`rfq` before sending the request. A `202 Accepted` response contains a Paradex
`request_id` and confirms only that the command was queued. The later
WebSocket `RESULT` event with the same `request_id` reports whether the venue
accepted the cancellation. RFQ lifecycle events report the eventual closed
state.

The `rfq_id` is the venue-issued identifier returned by a successful create
result or by the RFQ list endpoint.

An account holds only one RFQ open at a time, so this is also the request that
frees it to create the next one. The `RESULT` event reporting the cancellation
accepted is the point at which it is normally free; a create sent immediately
after may still be rejected for the RFQ being open, and can be retried.

## Path parameters

- `rfq_id` string, required

## Response `202`

Accepted

- ResponsesRfqAcceptedResponse
  - `accepted_at` integer — Unix milliseconds when the request was queued
  - `request_id` string — request_id identifies this request. It is echoed on the RESULT event delivered later on the WebSocket rfq channel, so a client with several requests in flight can match each outcome to the request that caused it. On Create it is the only identifier available until the venue issues the rfq_id.

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `403` — Forbidden

---

[API](https://skmtc.net/tradeparadex/apis/paradex-rest-api-2.md) · [All operations](https://skmtc.net/tradeparadex/apis/paradex-rest-api-2/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/tradeparadex/paradex-rest-api-2/revisions/e8fca3e578c7/schema)